Methods for Handling Radio Access Network Notification Area (RNA) Update Configuration Upon Reject

ABSTRACT

A wireless device handles area update reports. The wireless device initiates (1502) a radio network area update, RNAU, responsive to detecting that the wireless device has entered a cell not belonging to a radio network area, RNA, configured for the wireless device. The wireless device receives (1504), from the wireless network, a message indicating that the wireless device&#39;s attempt to perform the RNAU has been rejected. The message includes or is accompanied by an indication that a wait time value is applicable. Responsive to the message, the wireless device sets (1506) a reject wait timer to the wait time value and performs (1508) the RNAU upon expiry of the reject wait timer. In some embodiments, the wireless device sets a periodic RNAU timer to the wait time value, responsive to the message, and performs the RNAU upon expiry of the reject wait timer and the periodic RNAU timer.

BACKGROUND

Long Term Evolution (LTE) is an umbrella term for so-calledfourth-generation (4G) radio access technologies developed within theThird-Generation Partnership Project (3GPP) and initially standardizedin Releases 8 and 9, also known as Evolved UTRAN (E-UTRAN). LTE istargeted at various licensed frequency bands and is accompanied byimprovements to non-radio aspects commonly referred to as SystemArchitecture Evolution (SAE), which includes Evolved Packet Core (EPC)network. LTE continues to evolve through subsequent releases that aredeveloped according to standards-setting processes with 3GPP and itsworking groups (WGs), including the Radio Access Network (RAN) WG, andsub-working groups (e.g., RAN1, RAN2, etc.).

LTE Release 10 (Rel-10) supports bandwidths larger than 20 MHz. Oneimportant requirement on Rel-10 is to assure backward compatibility withLTE Release-8. This should also include spectrum compatibility. As such,a wideband LTE Rel-10 carrier (e.g., wider than 20 MHz) should appear asa number of carriers to an LTE Rel-8 (“legacy”) terminal. Each suchcarrier can be referred to as a Component Carrier (CC). For an efficientuse of a wide carrier also for legacy terminals, legacy terminals can bescheduled in all parts of the wideband LTE Rel-10 carrier. One exemplaryway to achieve this is by means of Carrier Aggregation (CA), whereby aRel-10 terminal can receive multiple CCs, each preferably having thesame structure as a Rel-8 carrier. Similarly, one of the enhancements inLTE Rel-11 is an enhanced Physical Downlink Control Channel (ePDCCH),which has the goals of increasing capacity and improving spatial reuseof control channel resources, improving inter-cell interferencecoordination (ICIC), and supporting antenna beamforming and/or transmitdiversity for control channel.

An overall exemplary architecture of a network comprising LTE and SAE isshown in FIG. 1. E-UTRAN 100 comprises one or more evolved Node B's(eNB), such as eNBs 105, 110, and 115, and one or more user equipment(UE), such as UE 120. As used within the 3GPP standards, “userequipment” or “UE” means any wireless communication device (e.g.,smartphone or computing device) that is capable of communicating with3GPP-standard-compliant network equipment, including E-UTRAN as well asUTRAN and/or GERAN, as the third- (“3G”) and second-generation (“2G”)3GPP radio access networks are commonly known.

As specified by 3GPP, E-UTRAN 100 is responsible for all radio-relatedfunctions in the access network, including radio bearer control, radioadmission control, radio mobility control, scheduling, and dynamicallocation of resources to UEs in uplink and downlink, as well assecurity of the communications with the UE. These functions reside inthe eNBs, such as eNBs 105, 110, and 115. The eNBs in the E-UTRANcommunicate with each other via the X1 interface, as shown in FIG. 1.The eNBs also are responsible for the E-UTRAN interface to the EPC,specifically the S1 interface to the Mobility Management Entity (MME)and the Serving Gateway (SGW), shown collectively as MME/S-GWs 134 and138 in FIG. 1. Generally speaking, the MME/S-GW handles both the overallcontrol of the UE and data flow between the UE and the rest of the EPC.More specifically, the MME processes the signaling protocols between theUE and the EPC, which are known as the Non-Access Stratum (NAS)protocols. The S-GW handles all Internet Protocol (IP) data packetsbetween the UE and the EPC, and serves as the local mobility anchor forthe data bearers when the UE moves between eNBs, such as eNBs 105, 110,and 115.

FIG. 2A shows a high-level block diagram of an exemplary LTEarchitecture in terms of its constituent entities—UE, E-UTRAN, andEPC—and high-level functional division into the Access Stratum (AS) andthe Non-Access Stratum (NAS). FIG. 1 also illustrates two particularinterface points, namely Uu (UE/E-UTRAN Radio Interface) and S1(E-UTRAN/EPC interface), each using a specific set of protocols, i.e.,Radio Protocols and S1 Protocols. Each of the two protocols can befurther segmented into user plane (or “U-plane”) and control plane (or“C-plane”) protocol functionality. On the Uu interface, the U-planecarries user information (e.g., data packets) while the C-plane iscarries control information between UE and E-UTRAN.

FIG. 2B illustrates a block diagram of an exemplary C-plane protocolstack on the Uu interface comprising Physical (PHY), Medium AccessControl (MAC), Radio Link Control (RLC), Packet Data ConvergenceProtocol (PDCP), and Radio Resource Control (RRC) layers. The PHY layeris concerned with how and what characteristics are used to transfer dataover transport channels on the LTE radio interface. The MAC layerprovides data transfer services on logical channels, maps logicalchannels to PHY transport channels, and reallocates PHY resources tosupport these services. The RLC layer provides error detection and/orcorrection, concatenation, segmentation, and reassembly, reordering ofdata transferred to or from the upper layers. The PHY, MAC, and RLClayers perform identical functions for both the U-plane and the C-plane.The PDCP layer provides ciphering/deciphering and integrity protectionfor both U-plane and C-plane, as well as other functions for the U-planesuch as header compression.

FIG. 2C shows a block diagram of an exemplary LTE radio interfaceprotocol architecture from the perspective of the PHY. The interfacesbetween the various layers are provided by Service Access Points (SAPs),indicated by the ovals in FIG. 2C. The PHY layer interfaces with the MACand RRC protocol layers described above. The MAC provides differentlogical channels to the RLC protocol layer (also described above),characterized by the type of information transferred, whereas the PHYprovides a transport channel to the MAC, characterized by how theinformation is transferred over the radio interface. In providing thistransport service, the PHY performs various functions including errordetection and correction; rate-matching and mapping of the codedtransport channel onto physical channels; power weighting, modulation;and demodulation of physical channels; transmit diversity, beamformingmultiple input multiple output (MIMO) antenna processing; and providingradio measurements to higher layers, such as RRC.

Downlink (i.e., eNB to UE) physical channels provided by the LTE PHYinclude Physical Downlink Shared Channel (PDSCH), Physical MulticastChannel (PMCH), Physical Downlink Control Channel (PDCCH), RelayPhysical Downlink Control Channel (R-PDCCH), Physical Broadcast Channel(PBCH), Physical Control Format Indicator Channel (PCFICH), and PhysicalHybrid ARQ Indicator Channel (PHICH). In addition, the LTE PHY downlinkincludes various reference signals, synchronization signals, anddiscovery signals.

Uplink (i.e., UE to eNB) physical channels provided by the LTE PHYinclude Physical Uplink Shared Channel (PUSCH), Physical Uplink ControlChannel (PUCCH), and Physical Random-Access Channel (PRACH). Inaddition, the LTE PHY uplink includes various reference signalsincluding demodulation reference signals (DM-RS), which are transmittedto aid the eNB in the reception of an associated PUCCH or PUSCH; andsounding reference signals (SRS), which are not associated with anyuplink channel.

The multiple access scheme for the LTE PHY is based on OrthogonalFrequency Division Multiplexing (OFDM) with a cyclic prefix (CP) in thedownlink, and on Single-Carrier Frequency Division Multiple Access(SC-FDMA) with a cyclic prefix in the uplink. To support transmission inpaired and unpaired spectrum, the LTE PHY supports both FrequencyDivision Duplexing (FDD) (including both full- and half-duplexoperation) and Time Division Duplexing (TDD). FIG. 3A shows an exemplaryradio frame structure (“type 1”) used for LTE FDD downlink (DL)operation. The DL radio frame has a fixed duration of 10 ms and consistsof 20 slots, labeled 0 through 19, each with a fixed duration of 0.5 ms.A 1-ms subframe comprises two consecutive slots where subframe iconsists of slots 2i and 2i+1. Each exemplary FDD DL slot consists ofN^(DL) _(symb) OFDM symbols, each of which is comprised of N_(se) OFDMsubcarriers. Exemplary values of N^(DL) _(symb) can be 7 (with a normalCP) or 6 (with an extended-length CP) for subcarrier bandwidth of 15kHz. The value of N_(sc) is configurable based upon the availablechannel bandwidth. Since persons of ordinary skill in the art arefamiliar with the principles of OFDM, further details are omitted inthis description.

As shown in FIG. 3A, a combination of a particular subcarrier in aparticular symbol is known as a resource element (RE). Each RE is usedto transmit a particular number of bits, depending on the type ofmodulation and/or bit-mapping constellation used for that RE. Forexample, some REs may carry two bits using QPSK modulation, while otherREs may carry four or six bits using 16- or 64-QAM, respectively. Theradio resources of the LTE PHY are also defined in terms of physicalresource blocks (PRBs). A PRB spans N^(RB) _(sc) sub-carriers over theduration of a slot (i.e., N^(DL) _(symb) symbols), where N^(RB) _(sc) istypically either 12 (with a 15-kHz sub-carrier bandwidth) or 24 (7.5-kHzbandwidth). A PRB spanning the same N^(RB) _(sc) subcarriers during anentire subframe (i.e., 2N^(DL) _(symb) symbols) is known as a PRB pair.Accordingly, the resources available in a subframe of the LTE PHY DLcomprise N^(DL) _(RB) PRB pairs, each of which comprises 2N^(DL)_(symb)·N^(RB) _(sc) REs. For a normal CP and 15-KHz sub-carrierbandwidth, a PRB pair comprises 168 REs.

FIG. 3B shows an exemplary LTE 1-DD uplink (UL) radio frame configuredin a similar manner as the exemplary FDD DL radio frame shown in FIG.3A. Using terminology consistent with the above DL description, each ULslot consists of N^(UL) _(symb) OFDM symbols, each of which is comprisedof N_(sc) OFDM subcarriers.

As discussed above, the LTE PHY maps the various DL and UL physicalchannels to the resources shown in FIGS. 3A and 3B, respectively. Forexample, the PHICH carries HARQ feedback (e.g., ACK/NAK) for ULtransmissions by the UEs. Similarly, PDCCH carries schedulingassignments, channel quality feedback (e.g., CSI) for the UL channel,and other control information. Likewise, a PUCCH carries uplink controlinformation such as scheduling requests, CSI for the downlink channel,HARQ feedback for eNB DL transmissions, and other control information.Both PDCCH and PUCCH can be transmitted on aggregations of one orseveral consecutive control channel elements (CCEs), and a CCE is mappedto the physical resource based on resource element groups (REGs), eachof which is comprised of a plurality of REs. For example, a CCE cancomprise nine (9) REGs, each of which can comprise four (4) REs.

While LTE was primarily designed for user-to-user communications, 5G(also referred to as “NR”) cellular networks are envisioned to supportboth high single-user data rates (e.g., 1 Gb/s) and large-scale,machine-to-machine communication involving short, bursty transmissionsfrom many different devices that share the frequency bandwidth. The 5Gradio standards (also referred to as “New Radio” or “NR”) are currentlytargeting a wide range of data services including eMBB (enhanced MobileBroad Band) and URLLC (Ultra-Reliable Low Latency Communication). Theseservices can have different requirements and objectives. For example,URLLC is intended to provide a data service with extremely strict errorand latency requirements, e.g., error probabilities as low as 10⁻⁵ orlower and 1 ms end-to-end latency or lower. For eMBB, the requirementson latency and error probability can be less stringent whereas therequired supported peak rate and/or spectral efficiency can be higher.

FIG. 4 illustrates a high-level view of the 5G network architecture,consisting of a Next Generation RAN (NG-RAN) and a 5G Core (5GC). TheNG-RAN can comprise a set of gNodeB's (gNBs) connected to the 5GC viaone or more NG interfaces, whereas the gNBs can be connected to eachother via one or more Xn interfaces. Each of the gNBs can supportfrequency division duplexing (FDD), time division duplexing (TDD), or acombination thereof.

The NG RAN logical nodes shown in FIG. 4 (and described in 3GPP TR38.801 v1.2.0) include a Central Unit (CU or gNB-CU) and one or moreDistributed Units (DU or gNB-DU). CU is a logical node that is acentralized unit that hosts high layer protocols and includes a numberof gNB functions, including controlling the operation of DUs. A DU is adecentralized logical node that hosts lower layer protocols and caninclude, depending on the functional split option, various subsets ofthe gNB functions. (As used herein, the terms “central unit” and“centralized unit” are used interchangeably, and the terms “distributedunit” and “decentralized unit” are used interchangeability.)

The NG, Xn-C and F1 items shown in FIG. 4 are logical interfaces. ForNG-RAN, the NG and Xn-C interfaces for a split gNB (e.g., consisting ofa gNB-CU and gNB-DUs) terminate in the gNB-CU. Likewise, for EN-DC, theS1-U and X2-C interfaces for a split gNB terminate in the gNB-CU. ThegNB-CU connects to gNB-DUs over respective F1 logical interfaces. ThegNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GCas a gNB, e.g., the F1 interface is not visible beyond gNB-CU.

Furthermore, a CU can host protocols such as RRC and PDCP, while a DUcan host protocols such as RLC, MAC and PHY. Other variants of protocoldistributions between CU and DU exist, such as hosting the RRC, PDCP andpart of the RLC protocol in CU (e.g., Automatic Retransmission Request(ARQ) function), while hosting the remaining parts of the RLC protocolin the DU, together with MAC and PHY. In some exemplary embodiments, CUis assumed to host RRC and PDCP, where PDCP is assumed to handle both UPtraffic and CP traffic. Nevertheless, other exemplary embodiments mayutilize other protocol splits that by hosting certain protocols in CUand certain others in the DU. Exemplary embodiments can also locatecentralized control plane protocols (e.g., PDCP-C and RRC) in adifferent CU with respect to the centralized user plane protocols (e.g.,PDCP-U).

In LTE Rel-13 a mechanism was introduced for the UE to be suspended bythe network in a suspended state similar to RRC_IDLE but with thedifference that the UE stores the Access Stratum (AS) context or RRCcontext. This makes it possible to reduce the signaling when the UEbecomes active again by resuming the RRC connection, thus eliminatingthe need to establish the RRC connection from scratch. Reducing thesignaling can have several benefits, including reduced UE latency (e.g.,for smart phones accessing the Internet) and reduced UE signaling, whichfurther leads to reduced UE energy consumption, particularly for machinetype communication (MTC) devices that send very little data (i.e.,signaling being a primary consumer of energy).

The LTE Rel-13 solution is based on the UE sending aRRCConnectionResume-Request message to the network and in responsereceiving an RRCConnectionResume message form the network. TheRRCConnectionResume is not encrypted, but is integrity protected.

As part of the 3GPP standardized work on 5G, it has been decided that NRshould support an RRC_INACTIVE state with similar properties as thesuspended state in LTE Rel-13. The RRC_INACTIVE state has slightlydifferent properties in that it is a separate RRC state and not part ofRRC_IDLE as in LTE. Additionally, the CN/RAN connection (NG or N2interface) is kept alive during RRC_INACTIVE while it was suspended inLTE.

FIG. 5A is an exemplary state transition diagram showing possibletransitions between RRC states in NR. The properties of the states shownin FIG. 5A are summarized as follows:

RRC_IDLE:

-   -   A UE specific DRX may be configured by upper layers;    -   UE controlled mobility based on network configuration;    -   The UE:    -   Monitors a Paging channel for CN paging using 5G-S-TMSI;    -   Performs neighbour cell measurements and cell (re-)selection;    -   Acquires system information.

RRC_INACTIVE:

-   -   A UE specific DRX may be configured by upper layers or by RRC        layer;    -   UE controlled mobility based on network configuration;    -   The UE stores the AS context;    -   The UE:    -   Monitors a Paging channel for CN paging using 5G-S-TMSI and RAN        paging using I-RNTI;    -   Performs neighboring cell measurements and cell (re-)selection;    -   Performs RAN-based notification area updates periodically and        when moving outside the RAN-based notification area;    -   Acquires system information.

RRC_CONNECTED:

-   -   The UE stores the AS context.    -   Transfer of unicast data to/from UE.    -   At lower layers, the UE may be configured with a UE specific        DRX;    -   For UEs supporting CA, use of one or more SCells, aggregated        with the SpCell, for increased bandwidth;    -   For UEs supporting DC, use of one SCG, aggregated with the MCG,        for increased bandwidth;    -   Network controlled mobility, i.e. handover within NR and to/from        E-UTRAN.    -   The UE:    -   Monitors a Paging channel;    -   Monitors control channels associated with the shared data        channel to determine if data is scheduled for it;    -   Provides channel quality and feedback information;    -   Performs neighbouring cell measurements and measurement        reporting;    -   Acquires system information.

FIG. 5B shows an exemplary flow diagram, between a user equipment (UE)and NR gNB, of various operations during a procedure for transition fromRRC_CONNECTED to RRC_INACTIVE. It has been agreed in 3GPP NRstandardization that the transition from RRC_CONNECTED to RRC_INACTIVEis done in one step, and, may contain a timer for periodic RANNotification Area (RNA) updates. It is assumed that the UE shall startthe timer (called T380) upon receiving the RRCSuspend (or equivalent)message shown in FIG. 5B. Is also assumed that the UE shall trigger aperiodic RNA update upon the expiry of T380. This is currently specifiedas follows in sections 5.3.14.3-4 of 3GPP TS 38.331:

5.3.14.3 Reception of the RRCSuspend by the UE

The UE shall:

-   -   1> delay the following actions defined in this sub-clause X ms        from the moment the RRCSuspend message was received or        optionally when lower layers indicate that the receipt of the        RRCSuspend message has been successfully acknowledged, whichever        is earlier;    -   Editor's Note: How to set the value of X (whether it is        configurable, or fixed to 60 ms as in LTE, etc.).    -   1> if the RRCSuspend message includes the        idleModeMobilityControlInfo:        -   2> store the cell reselection priority information provided            by the idleModeMobilityControlInfo;        -   2> if the t320 is included:            -   3> start timer T320, with the timer value set according                to the value of t320;    -   1> else:        -   2> apply the cell reselection priority information broadcast            in the system information;    -   1> store the following information provided by the network:        resumeIdentity, nextHopChainingCount, ran-Paging Cycle and        ran-NotificationAreaInfo;    -   1> re-establish RLC entities for all SRBs and DRBs;    -   1> reset MAC;    -   1> except if the RRCSuspend message was received in response to        an RRCResumeRequest:        -   2> store the UE AS Context including the current RRC            configuration, the current security context, the PDCP state            including ROHC state, C-RNTI used in the source PCell, the            cellIdentity and the physical cell identity of the source            PCell;    -   1> suspend all SRB(s) and DRB(s), except SRB0;    -   1> start timer T380, with the timer value set to        periodic-RNAU-timer;    -   1> indicate the suspension of the RRC connection to upper        layers;    -   1> configure lower layers to suspend integrity protection and        ciphering;    -   1> enter RRC_INACTIVE and perform procedures as specified in TS        38.304        5.3.14.4 T380 expiry or UE entering a cell not belonging to the        RNA        The UE shall:    -   1> if T380 expires:        -   2> initiate RRC connection resume procedure in 5.3.13 with            cause value set to ‘ffs’;    -   1> If UE entering a cell not belonging to the RNA:        -   2> initiate RRC connection resume procedure in 5.3.13 with            cause value set to ‘ffs’;

As it has been agreed that RNA updates (RNAUs) are performed using theRRC resume procedure, the procedures discussed below are performed upona UE entering a new RNA. More particularly, FIGS. 6A-6E show exemplaryflow diagrams of RRC connection resume procedures involving the UEsending a RRCResumeRequest message to the network, with various networkresponses. FIG. 6A shows a successful RRC connection resume. FIG. 6Bshows an RRCResumeRequest with fallback to RRC connection establishment,which is successful. FIG. 6C shows an RRCResumeRequest followed bynetwork release, which is successful. FIG. 6D shows an RRCResumeRequestfollowed by network suspend, which is successful. FIG. 6E shows anRRCResumeRequest followed by network rejection. Each of the networkresponses shown in FIGS. 6B-6E can be considered different ways ofrejecting the RRCResumeRequest, using different messages.

The UE initiates the RRC connection resume procedure upon request ofupper layers, when responding to NG-RAN paging, or upon triggering RNAupdates while the UE is in RRC_INACTIVE state. This is currentlyspecified in 3GPP TS 38.331 section 5.3.13.2, as follows:

5.3.13.2 Initiation

The UE initiates the procedure when upper layers request resume of anRRC connection, when responding to NG-RAN paging or upon triggering RNAupdates while the UE is in RRC_INACTIVE.Upon initiation of the procedure, the UE shall:

-   -   1> apply the default physical channel configuration as specified        in 9.2.4;    -   1> apply the default semi-persistent scheduling configuration as        specified in 9.2.3;    -   1> apply the default MAC main configuration as specified in        9.2.2;    -   1> apply the CCCH configuration as specified in 9.1.1.2;    -   1> start timer T300X;    -   1> stop timer T380;    -   1> initiate transmission of the RRCResumeRequest message in        accordance with 5.3.13.2 . . . .

For the scenario of RNA updates triggered while the UE is inRRC_INACTIVE state, the UE sends an RRCResumeRequest message with causevalue ‘ma-update’ (or equivalent). In response, if the network isoverloaded, it has been agreed that the network can send an RRCRejectmessage containing a wait timer, which corresponds to the flow diagramshown in FIG. 6E. The UE's handing of the RRCReject message is currentlyspecified as:

5.3.13.8 Reception of the RRCReject by the UE

The UE shall:

-   -   1> stop timer T314;    -   1> reset MAC and release the MAC configuration;    -   1> start timer T302, with the timer value set to the waitTime;    -   1> if RRCReject is sent in response to an RRCResumeResquest        triggered by upper layers;        -   2> inform upper layers about the failure to resume the RRC            connection and access control related information, upon            which the procedure ends;

SUMMARY

There is currently no specification of the action(s) to be taken by theUE upon receiving an RRCReject, as shown in FIG. 6E in response to anRRCResumeRequest triggered due, for example, to periodic RNA. Theinitiation of the resume procedure could be for different reasons, e.g.:

-   -   Upon UE entering a cell that does not belong to its configured        RNA, the UE shall perform RNA Update i.e. trigger an RRC Resume        procedure by sending an RRC Resume Request message with cause        value ‘ma-update’ (or equivalent);    -   Upon arrival of uplink data the UE shall perform an RRC Resume        procedure by sending an RRC Resume Request message with cause        value ‘mo-data’ (or equivalent); or    -   Upon UE receiving a RAN page message containing the I-RNTI which        has been assigned to the UE the UE shall perform an RRC Resume        procedure by sending an RRC Resume Request message with cause        value ‘ran-paging’ (or equivalent)

Upon receiving an RRC Reject in response to a Resume Request triggeredby the RRC layer such as mobility RNA (i.e., UE entering a cell notbelonging to its configured RNA), UL data, RAN paging, there is nodescription of subsequent action. According to conventional approaches,it is not certain which action the UE would take and what happens withthe RRC layer functionality (RNA Update, UL data, RAN page response) inthis case. In addition to that, the only described action says that theUE inform upper layers about the failure to resume the RRC connectionand access control related information, upon which the procedure ends,while in reality, RNA update and the other procedures are handled byRRC/Access Stratum layer.

In the specific case of mobility RNA updates, sine the RRC Reject may besent on SRB0, it is also uncertain to the UE whether the network hasbeen updated about the UE location or not, i.e., there might be someuncertainty on how the network should try to reach the RRC_INACTIVE UEvia RAN paging.

Another procedure that remains unclear is when the UE has sent an RRCResume Request for a mobility RNA update, received in response an RRCReject, started the wait timer, and while the wait timer is running, theUE performs cell reselection possible even to a cell which belongs tothe RNA the UE was configured with.

Exemplary embodiments disclosed herein address these problems, issues,and/or drawbacks of existing solutions, by providing new mechanisms forhandling UE actions upon receiving an RRC Reject (with wait timer) inresponse to RRC layer triggered procedures such as a mobility RNAUtriggered by the UE entering a cell that is outside the RNA configuredfor the UE. According to several of the disclosed embodiments, a clearUE behavior upon the reception of an RRC Reject in response to amobility RNA Update is defined, facilitating network actions in terms ofreachability via RAN paging. The techniques may also be used to avoidthat the UE ends up in a state or cell where it is no longer reachableby the network and higher layer services. More generally, the mechanismsdescribed herein avoid ambiguity in terms of state mismatch between UEand network.

Exemplary embodiments of the present disclosure include methods and/orprocedures for handling area update reports. According to someembodiments, a method in a wireless device includes initiating an RNAU,responsive to detecting that the wireless device has entered a cell notbelonging to an RNA configured for the wireless device and receiving,from the wireless network, a message indicating that the wirelessdevice's attempt to perform the RNAU has been rejected. The messageincludes or is accompanied by an indication that a wait time value isapplicable. The method also includes, responsive to the message, settinga reject wait timer to the wait time value. The method further includesperforming the RNAU upon expiry of the reject wait timer. In someembodiments, the wireless device also sets a periodic RNAU timer to thewait time value, responsive to the message, and performs the RNAU uponexpiry of the reject wait timer and the periodic RNAU timer.

According to some embodiments, a method in a wireless device operatingin a wireless network for handling area update reports includesinitiating a combined RNAU and TAU, responsive to detecting that thewireless device has entered a cell not belonging to an RNA configuredfor the wireless device and not belonging to a tracking area configuredfor the wireless device. The method includes receiving, from thewireless network, a message indicating that the wireless device'sattempt to perform the combined RNAU and TAU has been rejected. Themessage includes or is accompanied by an indication that a wait timevalue is applicable. The method also includes, responsive to themessage, setting a reject wait timer to the wait time value andsubsequently performing a cell reselection, prior to expiry of theperiodic RNAU timer. The method further includes immediately performinga TAU, subsequent to the cell reselection.

According to some embodiments, a method in a wireless device operatingin a wireless network for handling area update reports includesinitiating a RNAU, responsive to detecting that the wireless device hasentered a cell not belonging to an RNA configured for the wirelessdevice. The method also includes receiving, from the wireless network, amessage indicating that the wireless device's attempt to perform theRNAU has been rejected, the message comprising or being accompanied byan indication that a wait time value is applicable. The method furtherincludes, responsive to the message, setting a reject wait timer to thewait time value, and notifying the wireless device's RRC layer of therejection.

According to some embodiments, a method in a wireless device operatingin a wireless network for handling area update reports includesinitiating an RNAU, responsive to detecting that the wireless device hasentered a cell not belonging to an RNA configured for the wirelessdevice. The method includes receiving, from the wireless network, amessage indicating that the wireless device's attempt to perform theRNAU has been rejected, the message comprising or being accompanied byan indication that a wait time value is applicable. The method furtherincludes, responsive to the message, tracking the rejected RNAU as apending notification, such that the rejected RNAU is attempted again assoon as allowed and/or as soon as certain conditions are met.

Other exemplary embodiments include radio nodes in the cellular network(e.g., radio nodes (e.g., base stations, low-power nodes, wirelessdevices, user equipment, etc.) configurable to perform operationscorresponding to the exemplary methods and/or procedures describedabove. Other exemplary embodiments include non-transitory,computer-readable media storing program instructions that, when executedby at least one processor, configure such radio nodes to performoperations corresponding to the exemplary methods and/or proceduresdescribed above.

These and other objects, features and advantages of the exemplaryembodiments of the present disclosure will become apparent upon readingthe following detailed description of the exemplary embodiments of thepresent disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high-level block diagram of an exemplary architecture of theLong-Term Evolution (LTE) Evolved UTRAN (E-UTRAN) and Evolved PacketCore (EPC) network, as standardized by 3GPP.

FIG. 2A is a high-level block diagram of an exemplary E-UTRANarchitecture in terms of its constituent components, protocols, andinterfaces.

FIG. 2B is a block diagram of exemplary protocol layers of thecontrol-plane portion of the radio (Uu) interface between a userequipment (UE) and the E-UTRAN.

FIG. 2C is a block diagram of an exemplary LTE radio interface protocolarchitecture from the perspective of the PHY layer.

FIGS. 3A and 3B are block diagrams of exemplary downlink and uplink,respectively, LTE radio frame structures used for frequency divisionduplexing (FDD) operation.

FIG. 4 shows a block diagram of an exemplary 5G logical networkarchitecture.

FIGS. 5A and 5B show an exemplary state transition diagram and exemplaryflow diagram, respectively, showing possible transitions between RRCstates in NR.

FIGS. 6A, 6B, 6C, 6D, and 6E show exemplary flow diagrams of RRCconnection resume procedures involving the UE sending a RRCResumeRequestmessage to the network, with various network responses, according tovarious exemplary embodiments of the present disclosure.

FIG. 7 illustrates an example communication system, according to someembodiments.

FIG. 8 is a generalized block diagram of a host computer communicatingvia a base station with a user equipment over a partially wirelessconnection, according to some embodiments.

FIG. 9-12 are flowcharts illustrating methods implemented in acommunication system including a host computer, a base station and auser equipment.

FIG. 13 is a block diagram illustrating an example network node,according to some embodiments.

FIG. 14 is a block diagram illustrating an example wireless device,according to some embodiments.

FIG. 15 is a process flow diagram illustrating an example methodaccording to some embodiments, as carried out in the wireless device.

FIG. 16 is a process flow diagram illustrating another example methodaccording to some embodiments, as carried out in the wireless device.

FIG. 17 is a process flow diagram illustrating another example methodaccording to some embodiments, as carried out in the wireless device.

FIG. 18 is a process flow diagram illustrating another example methodaccording to some embodiments, as carried out in the wireless device.

FIG. 19 is a block diagram illustrating a functional representation ofan example wireless device.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art. Furthermore, the following terms are usedthroughout the description given below:

-   -   Radio Node: As used herein, a “radio node” can be either a        “radio access node” or a “wireless device.”    -   Radio Access Node: As used herein, a “radio access node” (or        “radio network node”) can be any node in a radio access network        (RAN) of a cellular communications network that operates to        wirelessly transmit and/or receive signals. Some examples of a        radio access node include, but are not limited to, a base        station (e.g., a New Radio (NR) base station (gNB) in a 3GPP        Fifth Generation (5G) NR network or an enhanced or evolved Node        B (eNB) in a 3GPP LTE network), a high-power or macro base        station, a low-power base station (e.g., a micro base station, a        pico base station, a home eNB, or the like), and a relay node.    -   Core Network Node: As used herein, a “core network node” is any        type of node in a core network. Some examples of a core network        node include, e.g., a Mobility Management Entity (MME), a Packet        Data Network Gateway (P-GW), a Service Capability Exposure        Function (SCEF), or the like.    -   Wireless Device: As used herein, a “wireless device” is any type        of device that has access to (i.e., is served by) a cellular        communications network by wirelessly transmitting and/or        receiving signals to a radio access node(s). Some examples of a        wireless device include, but are not limited to, a UE in a 3GPP        network and a Machine Type Communication (MTC) device.    -   Network Node: As used herein, a “network node” is any node that        is either part of the radio access network or the core network        of a cellular communications network/system.

Note that the description given herein focuses on a 3GPP cellularcommunications system and, as such, 3GPP terminology or terminologysimilar to 3GPP terminology is oftentimes used. However, the conceptsdisclosed herein are not limited to a 3GPP system. Furthermore, althoughthe term “cell” is used herein, it should be understood that(particularly with respect to 5G NR concepts) beams may be used insteadof cells and, as such, concepts described herein apply equally to bothcells and beams.

Various exemplary embodiments are described herein as methods,procedures, and/or operations performed by a UE in RRC_INACTIVE state inan NR network. These embodiments are used for the purpose ofillustration only, without limitation. For example, principles of theseembodiments are equally applicable to other configurations, scenarios,and/or network types included, but not limited to:

-   -   UEs in RRC_INACTIVE state in LTE networks;    -   UE inter-RAT procedures in RRC_INACTIVE, mainly between LTE and        NR RANs connected to the same CN (5G Core Network). In these        scenarios, the periodic RNA update timer, T380, is defined as an        inter-RAT timer (i.e., it keeps running even when UE is changing        RAT). If T380 expires when the UE is in the other RAT, the UE        will perform periodic RNA update in that RAT. These inter-RAT        scenarios include:        -   UE in LTE RRC_CONNECTED is suspended to LTE RRC_INACTIVE,            starts T380, performs mobility management and camps on an NR            cell (i.e. becomes RRC_INACTIVE in NR). While in NR, T380            expires and UE tries to perform an RNA update (with a resume            request) in NR. Network can respond with an RRCReject.        -   UE in NR RRC_CONNECTED is suspended to NR RRC_INACTIVE,            starts T380, performs mobility management, and camps on an            LTE cell (i.e. becomes RRC_INACTIVE in LTE). While in LTE,            T380 expires and UE tries to perform an RNA update (with a            resume request) in NR. Network can respond with an            RRCReject.

Various exemplary embodiments are described herein as methods,procedures, and/or operations performed by a UE upon receiving anRRCReject message with a wait timer. These embodiments are used for thepurpose of illustration only, without limitation. For example,principles of these embodiments are equally applicable to otherconfigurations, scenarios, and/or network types involving a “rejectfunctionality” by the network but without using this exact message. Forexample, an RRC Release or RRC Release with suspend configuration mayalso include a wait timer indicating that the UE shall not access thesystem until that timer expires (or the UE performs cell reselection).In the event that the system supports the “reject functionality” viaRRCReject or RRC Release, there may also be differences in UE behaviordepending which message the network uses to respond to the UE. Forexample, the RRCReject is typically sent using SRB0, which isunprotected, while RRC Release with suspend indication (or equivalentmessage) moving UEs to RRC_INACTIVE state uses SRB1, which is protectedand secure. These aspects are discussed later with respect to variousembodiments.

Also notable is that the specific techniques described below aredescribed in the context of mobility-triggered RNA updates. Thetechniques, however, may be also applicable to other scenarios in whichthe RRC resume procedure is triggered, e.g., in response to a RAN pageor the availability of uplink (UL) data.

In a first approach, comprising several possible embodiments, the UE,which may be more generally referred to as a wireless device, sets theperiodic RNAU timer to the wait timer value, upon receiving a messagerejecting the UE with a wait time (e.g., RRC Reject or Release with await timer), where the message is in response to a mobility RNA update(e.g., triggered by the UE entering a cell not belonging to itsconfigured RNA). The UE starts the reject wait timer (e.g., T302 in NRdraft specifications), sets the periodic RNAU timer T380 to the samevalue used to set the wait timer T302, and starts the periodic RNAUtimer. Consequently, the UE performs a periodic RNAU attempt immediatelyafter the wait timer T302 expires. This approach is particularly usefulin the event that the rejecting message is sent on SRB0, since if thismessage was sent in SRB1, instead, the network would be able to updatethe context and explicitly provide a periodic RNAU timer. One advantageof setting the periodic RNAU timer to the wait timer is that the UEbehaves according to the behavior defined according to the periodic RNAUtimer, without the need to specify exceptional actions, and withoutmaking the mobility RNAU pending. This may speed up the notificationthat the UE has changed RNAs, in many circumstances

It may be observed that by setting the periodic RNAU timer to the waittimer, the UE will not perform a mobility RNAU upon cell reselection,even though the wait timer will expire and the UE is then allowed toaccess the system. This may be considered an especially useful result ifit is desired to avoid unnecessary signaling, with necessary paging inthis situation handled via core network paging.

From a network perspective, it may be observed that the described UEbehavior may lead to the network not receiving a mobility RNAU when theUE enters a cell not belonging to its configured RNA. However, since thenetwork knows that a Reject may occur due to Reject in a specific cellwithout necessarily updating the UE context about that Rejectoccurrence, the network may still assume the UE is in coverage, althoughpossibly not in its configured RNA. The network may be configured to tryto page the UE in the configured TAI list, for example, if the initialattempt in the UE's RNA fails. Hence, the network may anyway try to pagethe UE with RAN paging.

In a variant of the approach described above, the UE sets the periodicRNAU timer to the value of the wait timer only if it receives anindication in the RRC Reject message from the network. That indicationmay be something the network sets if it has the UE context available butstill prefers to reject the UE.

In another variant to the above approaches, upon receiving the rejectingmessage in response to a mobility RNA update, the UE starts the rejectwait timer (e.g., T302 in NR draft specifications), re-starts theperiodic RNAU timer to a default value, and notifies RRC layer.

In yet another variant to the above approaches, a slightly differentbehavior can be defined in the event that the rejected mobility RNAU isactually a combined mobility RNAU and TAU. Upon receiving the rejectingmessage in response to a mobility RNA update, the UE starts the rejectwait timer (e.g., T302 in NR draft specifications), re-starts theperiodic RNAU timer to a value, and notifies RRC layer. If cellreselection occurs, the UE immediately perform a Tracking Area Update.

According to another set of techniques, the concept of a pendingnotification is applied to the problems discussed above. In someembodiments, then, upon receiving the rejecting message (e.g., RRCReject with wait timer) in response to a mobility RNA update (or otherResume cases), the UE starts the reject wait timer (e.g., T302 in NRdraft specifications), and notifies RRC layer, so that the RRC layer (orAS layer) makes that mobility RNA update (or other Resume cases e.g. ULdata, RAN page response) a pending notification that is tracked by theUE.

By making that a pending notification, the UE attempts to re-performResume procedure as soon as the UE is allowed to. For example:

-   -   Upon the expiry of the wait timer T302, the RRC layer (or AS        layer) requests the UE to perform the pending Resume procedure        (e.g., mobility RNAU).

In a variant, that subsequent Resume procedure, which was pending,contains an indication that this is not the first attempt but a pendingnotification. That may indicate to the network that this is a latenotification. This may be useful in case the network has tried to pagethe UE without success in its RNA while T302 was running (i.e., the UEwas rejected upon trying to perform a mobility RNA in the cell notbelonging to its configured RNA).

From a network perspective (e.g., for the mobility-triggered RNAU case),it may be observed that by making the mobility RNAU pending at the UE,the network knows it should receive the mobility RNAU as soon as the UEis allowed to send it, which may simplify the network's RAN pagingaction. While T302 is running, the network may try to page the UE in itsRNA without a UE response, but it can subsequently try CN paging toreach the UE in a cell not belonging to its RNA. An additional problemmay occur if that mobility RNA is a combined RNA with TAU, i.e., wherethe UE is in a cell that is not within its TAI list. In that case, thefollowing variants are defined:

-   -   If the mobility RNAU that is pending is a combined RNAU and TAU,        i.e. UE is crossing the RNA border and the TAU border at the        same time, the resume request has a cause value ‘mo-signalling’        and should have higher priority in the access control policies        otherwise the UE may become unreachable for both RAN and CN        paging. Another variant is to define a cause value for this        combined RNA/TAU instead of simply saying this is mo-signalling.        Another alternative is the network implementation prioritize        these resume request.

In some circumstances, the first allowed opportunity to re-perform theResume procedure may be upon cell reselection, upon which the UEperforms the pending Resume procedure (e.g., mobility RNAU) in variousembodiments. In a variant, this subsequent Resume procedure may containan indication that this is not the first attempt. That may be useful tothe network in case the UE attempts to performs mobility RNAU because ithas entered a cell not in its configured RNA, it is rejected by thenetwork and starts T302, and, performs cell reselection to a cell thatis within its configured RNA again while T302 is running.

From a network perspective, it may be observed that the UE may re-selectto a cell that is again within its configured RAN. However, sending thepending RNA allows the network to figure out what has happened, e.g., inthe event that the network tried to page the UE via RAN paging and theUE has not responded.

In another variant to the above approaches where the Resume procedurebecomes pending, the timer T380 is not modified upon the reception ofthe rejecting message, in some embodiments, which may simplify networkimplementation since the network may still wait for periodic RNAUsregardless of the rejecting scenarios.

In some embodiments, the pending procedure is changed due to changing ofany of the following conditions:

-   -   the UE enters a new cell,    -   the UE gets a higher priority procedure, or    -   the UE is forbidden to access target cell.

According to another set of techniques, closely related to thosedescribed immediately above, the Resume procedure becomes pending onlyunder certain conditions. In some embodiments, upon receiving therejecting message (e.g. RRC Reject with wait timer) in response to aResume request message, the UE starts the reject wait timer (e.g. T302in NR draft specifications), and notifies RRC layer, so the RRC layer(or AS layer) makes that Resume procedure a pending notification. but itdoes not necessarily trigger the pending Resume procedure when it isallowed, only when certain conditions are fulfilled, as described below:

-   -   Upon the expiry of the wait timer T302, the UE only performs the        pending mobility RNAU again if upon the timer expires the UE is        still camping on a cell that is not within its configured RNA.        If upon the timer expiry the UE is in its configured RNA, the UE        discards the pending mobility RNA update.    -   Upon cell reselection, the UE performs the pending mobility RNAU        only if the new cell does not belong to its configured RNA. In        other words, if the UE performs cell reselection while T302 is        running and the new cell belongs to the UE's configured RNA, the        UE discards the pending mobility RNA update.    -   Upon cell reselection and/or the expiry of the wait timer T302        only if the pending mobility RNAU is a combined RNA and Tracking        Area Update, i.e., the UE performs the pending mobility RNAU. In        another variant of this approach, upon cell reselection and/or        the expiry of the wait timer T302 only if the pending mobility        RNAU is a combined RNA and Tracking Area Update, i.e., the UE        performs a Tracking Area Update instead of the mobility RNAU,        since that enables the UE to update both RAN and CN of its        location.    -   Upon a higher priority even is triggered in the UE (e.g.,        emergency call) the pending Resume procedure is either        re-triggered again (regardless of whether T302 is running) or        the pending Resume procedure is discarded and instead only the        higher priority procedure is performed.    -   Upon cell reselection if the UE selects a cell which not        considered a suitable cell for camping (e.g. UE is forbidden to        access the cell). In this case the pending Resume procedure may        be discarded, or performed at a later stage when UE selects a        suitable cell.

In another variant of the approaches where the Resume procedure becomespending, the timer T380 is not modified upon the reception of therejecting message, which may simplify network implementation as thenetwork may still wait for periodic RNAUs regardless of the rejectingscenarios.

In yet another set of approaches, the Resume procedure is not pending.According to some embodiments, upon the expiry of the wait timer T302,the UE does not have to immediately send a Resume procedure (i.e., themessage is not considered pending by RRC and/or the higher layers), butsimply relies on the actions related to the Resume procedure uponreceiving the message rejecting the UE. That may create a temporaryreachability issue from the network side that could be solved via CNpaging. On the other hand, it may simplify significantly the UEbehavior.

In some embodiments, upon reject, the UE notifies higher layer and uponT302 expiry the UE perform Resume procedure. After receiving a rejectmessage after trying to perform a mobility RNAU or other Resumeprocedure, the UE notifies the higher layers and, upon the expiry of thewait timer T302, the UE immediately performs a Tracking AreaUpdate/Registration Area Update or other NAS recovery procedure. In thisway the UE-RAN state would be re-build from the Core Network. Thissolution is useful e.g. if the UE has moved into a different CN area andhas been unreachable from the network during the wait time.

In a variant of this latter approach, upon the expiry of T302, the UEdiscards the UE context, enters RRC_IDLE from RRC_INACTIVE, and performsthe NAS level procedure.

In some embodiments, when the UE is rejected upon trying to perform amobility RNAU, the UE starts the wait timer T302 and continues tomonitor RAN paging notifications according to its stored configuration(provided when the UE was moved to RRC_INACTIVE, i.e., not in themessage rejecting the UE). The UE continues to monitor RAN paging, sincethe network may either know the current UE location (current cell thatit is camping) despite the rejection of the mobility RNA update.

In corresponding embodiments from a network perspective, if the networkis aware of the UE location after rejecting a request of RNA update, thenetwork may perform RAN paging in the new cell the UE is camping on(i.e., the cell the UE was rejected) despite that the camping cell doesnot necessarily belong to the configured RNA of that UE.

In some embodiments, when the UE is rejected upon trying to perform amobility RNAU, the UE starts the wait timer T302 and stops monitoringRAN paging notifications according to its stored configuration (providedwhen the UE was moved to RRC_INACTIVE, i.e., not in the messagerejecting the UE) and only monitors CN paging. UE continues to monitorCN paging to save battery, as the network may anyway not know thecurrent UE location (current cell that it is camping).

In corresponding embodiments from a network perspective, the rejectingmessage is send on SRB0, the network may reject the UE without updatingthe UE context. Hence, the node where the UE has tried to perform themobility RNAU may not even try to fetch the context. And, if a pagingnotification comes in the node where the context is, the node may tryRAN paging in the UE's configured RNA and if that fails, the network mayactually try CN paging. As the RAN paging will anyway fail, uponentering the new RNA and being rejected it might be useful not tocontinue monitoring RAN paging for the UE as network may not try thatanyway.

In yet other embodiments, the network may include in the Reject messagean indication to the UE on whether the UE shall continue to perform RANpaging or not. That indication is basically a way to indicate the UEthat the node having the UE context is aware of the UE's location on acell level.

In some embodiments, the UE stores information about the reception ofmessages rejecting the UE from the network. The information about therejection may contain, for example:

-   -   A counter that is incremented at each rejected attempt. That        counter may be specific per cause value, i.e., in this specific        case for periodic RNAUs.    -   The exact location where the UE was rejected, for example,        adding to the report the PCI and/or cell identifier and/or        global cell identifier and/or PLMN for each rejected attempt.

The information described above may be used in different ways. Forexample, a report can be created from that stored information andreported to the network when the UE enters RRC_CONNECTED. Another usagecould be to use the information as input to an access control functionso that if a RNAU is triggered while T302 is running, depending on thenumber of frustrated attempts of RNAUs, access control function mayauthorize the UE to send a resume request with RNAU.

In other embodiments, a protection mechanism is defined where after XRNAU attempts followed by network reject (where X can either be fixed bythe standard or configurable), the UE perform different actions:

-   -   In one variant, the UE discards its UE context and notifies the        higher layers and/or the RRC layer. Then, immediately after the        UE can access the network again (e.g. upon the expiry of T302 or        upon cell reselection) it performs a NAS recovery;    -   In another variant, the UE performs inter-frequency cell        reselection or inter-RAT cell reselection and tries to perform a        periodic RNAU.

Some of the techniques described above may be implemented in the NR RRCspecifications as follows. First, the approaches where the periodic RNAUtimer is re-started may be implemented according to:

0.3.13.8 Reception of the RRCReject by the UE

The UE shall:

-   -   1> stop timer T314;    -   1> reset MAC and release the MAC configuration;    -   1> start timer T302, with the timer value set to the waitTime;    -   1> re-start the periodic RNAU timer T380 to the value set to        waitTime;    -   1> if RRCReject is sent in response to an RRCResumeResquest        triggered by upper layers;        -   2> inform upper layers about the failure to resume the RRC            connection and access control related information, upon            which the procedure ends;

Embodiments where the mobility RNAU becomes pending may be implementedaccording to:

5.3.13.8 Reception of the RRCReject by the UE

The UE shall:

-   -   1> stop timer T314;    -   1> reset MAC and release the MAC configuration;    -   1> start timer T302, with the timer value set to the waitTime;    -   1> stop T380, if running;    -   1> if RRCReject is sent in response to an RRCResumeResquest        triggered by upper layers;        -   2> inform upper layers about the failure to resume the RRC            connection and access control related information, upon            which the procedure ends;    -   1> if RRCReject is sent in response to an RRCResumeRequest due        to mobility (i.e. upon entering a cell not belonging to its        configured RNA);        -   2> inform RRC layer (or AS layer) about the failure to            resume the RRC connection and access control related            information (i.e. due to reject with wait timer), which will            consider the RNAU as pending, upon which the procedure ends;            . . .            5.3.13.6 Cell re-selection while T314 or T302 is running            . . .            The UE shall:    -   1> if cell reselection occurs while T314 or T302 is running:        -   3> stop timer T314 if running;        -   3> stop timer T302 if running;        -   3> reset MAC, release the MAC configuration and re-establish            RLC for all RBs that are established;        -   3> discard the temporary security context (previously            restored) and the keys K_(RRCenc) key, the K_(RRCint), the            K_(UPint) key and the K_(UPenc);        -   3> perform the RRC resume procedure procedure as specified            in 5.3.13;            5.3.13.x T302 expiry or stop            The UE shall:    -   1> if timer T302 expires or is stopped (e.g. upon cell        reselection):        -   2> inform upper layers about barring alleviation for mobile            terminating access and trigger any pending RNA updates;

Embodiments where, upon, reject, the UE notifies higher layers and uponT302 expiry the UE performs tracking area update may be implemented asfollows:

5.3.13.8 Reception of the RRCReject by the UE

The UE shall:

-   -   1> stop timer T314;    -   1> reset MAC and release the MAC configuration;    -   1> start timer T302, with the timer value set to the waitTime;    -   1> if RRCReject is sent in response to an RRCResumeResquest        triggered by upper layers;        -   2> inform upper layers about the failure to resume the RRC            connection and access control related information, upon            which the procedure ends;            . . .            5.3.13.6 Cell re-selection while T314 or T302 is running            . . .            The UE shall:            1> if cell reselection occurs while T314 or T302 is running:    -   3> stop timer T314 if running;    -   3> stop timer T302 if running;    -   3> reset MAC, release the MAC configuration and re-establish RLC        for all RBs that are established;    -   3> discard the temporary security context (previously restored)        and the keys K_(RRCenc) key, the K_(RRCint), the K_(UPint) key        and the K_(UPenc),    -   3> if an RRCResumeRequest is pending (e.g. due to access        control);        -   4> perform the RRC resume procedure procedure as specified            in 5.3.13;            5.3.13.x T302 expiry or stop            The UE shall:            1> if timer T302 expires or is stopped (e.g. upon cell            reselection):    -   2> inform upper layers about barring alleviation for mobile        terminating access and trigger any pending RNA updates;

FIG. 7, in accordance with various embodiments, shows a communicationsystem that includes a telecommunication network 710, such as a3GPP-type cellular network, which comprises an access network 711, suchas an gNB-RAN, and a core network 714 (e.g., 5GC). The access network711 comprises a plurality of base stations 712 a, 712 b, 712 c, such asgNBs or other types of wireless access points, each defining acorresponding coverage area 713 a, 713 b, 713 c. Each base station 712a, 712 b, 712 c is connectable to the core network 714 over a wired orwireless connection 715. A first user equipment (UE) 791 located incoverage area 713 c is configured to wirelessly connect to, or be pagedby, the corresponding base station 712 c. A second UE 792 in coveragearea 713 a is wirelessly connectable to the corresponding base station712 a. While a plurality of UEs 791, 792 are illustrated in thisexample, the disclosed embodiments are equally applicable to a situationwhere a sole UE is in the coverage area or where a sole UE is connectingto the corresponding base station 712.

The telecommunication network 710 is itself connected to a host computer730, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. The host computer 730 may beunder the ownership or control of a service provider or may be operatedby the service provider or on behalf of the service provider. Theconnections 721, 722 between the telecommunication network 710 and thehost computer 730 may extend directly from the core network 714 to thehost computer 730 or may go via an optional intermediate network 720.The intermediate network 720 may be one of, or a combination of morethan one of, a public, private or hosted network; the intermediatenetwork 720, if any, may be a backbone network or the Internet; inparticular, the intermediate network 720 may comprise two or moresub-networks (not shown).

The communication system of FIG. 7 as a whole enables connectivitybetween one of the connected UEs 791, 792 and the host computer 730. Theconnectivity may be described as an over-the-top (OTT) connection 750.The host computer 730 and the connected UEs 791, 792 are configured tocommunicate data and/or signaling via the OTT connection 750, using theaccess network 711, the core network 714, any intermediate network 720and possible further infrastructure (not shown) as intermediaries. TheOTT connection 750 may be transparent in the sense that theparticipating communication devices through which the OTT connection 750passes are unaware of routing of uplink and downlink communications. Forexample, a base station 712 may not or need not be informed about thepast routing of an incoming downlink communication with data originatingfrom a host computer 730 to be forwarded (e.g., handed over) to aconnected UE 791. Similarly, the base station 712 need not be aware ofthe future routing of an outgoing uplink communication originating fromthe UE 791 towards the host computer 730.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 8. In a communicationsystem 800, a host computer 810 comprises hardware 815 including acommunication interface 816 configured to set up and maintain a wired orwireless connection with an interface of a different communicationdevice of the communication system 800. The host computer 810 furthercomprises processing circuitry 818, which may have storage and/orprocessing capabilities. In particular, the processing circuitry 818 maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. The host computer 810further comprises software 811, which is stored in or accessible by thehost computer 810 and executable by the processing circuitry 818. Thesoftware 811 includes a host application 812. The host application 812may be operable to provide a service to a remote user, such as a UE 830connecting via an OTT connection 850 terminating at the UE 830 and thehost computer 810. In providing the service to the remote user, the hostapplication 812 may provide user data which is transmitted using the OTTconnection 850.

The communication system 800 further includes a base station 820provided in a telecommunication system and comprising hardware 825enabling it to communicate with the host computer 810 and with the UE830. The hardware 825 may include a communication interface 826 forsetting up and maintaining a wired or wireless connection with aninterface of a different communication device of the communicationsystem 800, as well as a radio interface 827 for setting up andmaintaining at least wireless connection 870 with the UE 830 located ina coverage area (not shown in FIG. 8) served by the base station 820.The communication interface 826 may be configured to facilitate aconnection 860 to the host computer 810. The connection 860 may bedirect or it may pass through a core network (not shown in FIG. 8) ofthe telecommunication system and/or through one or more intermediatenetworks outside the telecommunication system. In the embodiment shown,the hardware 825 of the base station 820 further includes processingcircuitry 828, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The base station 820 further has software 821 stored internally oraccessible via an external connection.

The communication system 800 further includes the UE 830 alreadyreferred to. Its hardware 835 may include a radio interface 837configured to set up and maintain a wireless connection 870 with a basestation serving a coverage area in which the UE 830 is currentlylocated. The hardware 835 of the UE 830 further includes processingcircuitry 838, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The UE 830 further comprises software 831, which is stored in oraccessible by the UE 830 and executable by the processing circuitry 838.The software 831 includes a client application 832. The clientapplication 832 may be operable to provide a service to a human ornon-human user via the UE 830, with the support of the host computer810. In the host computer 810, an executing host application 812 maycommunicate with the executing client application 832 via the OTTconnection 850 terminating at the UE 830 and the host computer 810. Inproviding the service to the user, the client application 832 mayreceive request data from the host application 812 and provide user datain response to the request data. The OTT connection 850 may transferboth the request data and the user data. The client application 832 mayinteract with the user to generate the user data that it provides.

It is noted that the host computer 810, base station 820 and UE 830illustrated in FIG. 8 may be identical to the host computer 730, one ofthe base stations 712 a, 712 b, 712 c and one of the UEs 791, 792 ofFIG. 7, respectively. This is to say, the inner workings of theseentities may be as shown in FIG. 8 and independently, the surroundingnetwork topology may be that of FIG. 7.

In FIG. 8, the OTT connection 850 has been drawn abstractly toillustrate the communication between the host computer 810 and the useequipment 830 via the base station 820, without explicit reference toany intermediary devices and the precise routing of messages via thesedevices. Network infrastructure may determine the routing, which it maybe configured to hide from the UE 830 or from the service provideroperating the host computer 810, or both. While the OTT connection 850is active, the network infrastructure may further make decisions bywhich it dynamically changes the routing (e.g., on the basis of loadbalancing consideration or reconfiguration of the network).

The wireless connection 870 between the UE 830 and the base station 820is in accordance with the teachings of the embodiments describedthroughout this disclosure. One or more of the various embodimentsimprove the performance of OTT services provided to the UE 830 using theOTT connection 850, in which the wireless connection 870 forms the lastsegment. More precisely, a clear UE behavior upon the reception of anRRC Reject in response to a mobility RNA Update is defined, facilitatingnetwork actions in terms of reachability via RAN paging. The techniquesmay also be used to avoid that the UE ends up in a state or cell whereit is no longer reachable by the network and higher layer services. Moregenerally, the mechanisms described herein avoid ambiguity in terms ofstate mismatch between UE and network. These embodiments will result inimproved performance, such as better and/or more consistent throughput,and/or reduced delays, for users of the RAN.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring the OTT connection 850 between the hostcomputer 810 and UE 830, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring the OTT connection 850 may be implemented in the software811 of the host computer 810 or in the software 831 of the UE 830, orboth. In embodiments, sensors (not shown) may be deployed in or inassociation with communication devices through which the OTT connection850 passes; the sensors may participate in the measurement procedure bysupplying values of the monitored quantities exemplified above or bysupplying values of other physical quantities from which software 811,831 may compute or estimate the monitored quantities. The reconfiguringof the OTT connection 850 may include message format, retransmissionsettings, preferred routing etc.; the reconfiguring need not affect thebase station 820, and it may be unknown or imperceptible to the basestation 820. Such procedures and functionalities may be known andpracticed in the art. In certain embodiments, measurements may involveproprietary UE signaling facilitating the host computer's 810measurements of throughput, propagation times, latency and the like. Themeasurements may be implemented in that the software 811, 831 causesmessages to be transmitted, in particular empty or ‘dummy’ messages,using the OTT connection 850 while it monitors propagation times, errorsetc.

FIG. 9 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 9will be included in this section. In a first step 910 of the method, thehost computer provides user data. In an optional substep 911 of thefirst step 910, the host computer provides the user data by executing ahost application. In a second step 920, the host computer initiates atransmission carrying the user data to the UE. In an optional third step930, the base station transmits to the UE the user data which wascarried in the transmission that the host computer initiated, inaccordance with the teachings of the embodiments described throughoutthis disclosure. In an optional fourth step 940, the UE executes aclient application associated with the host application executed by thehost computer.

FIG. 10 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 10will be included in this section. In a first step 1010 of the method,the host computer provides user data. In an optional substep (notshown), the host computer provides the user data by executing a hostapplication. In a second step 1020, the host computer initiates atransmission carrying the user data to the UE. The transmission may passvia the base station, in accordance with the teachings of theembodiments described throughout this disclosure. In an optional thirdstep 1030, the UE receives the user data carried in the transmission.

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 11will be included in this section. In an optional first step 1110 of themethod, the UE receives input data provided by the host computer.Additionally or alternatively, in an optional second step 1120, the UEprovides user data. In an optional substep 1121 of the second step 1120,the UE provides the user data by executing a client application. In afurther optional substep 1111 of the first step 2010, the UE executes aclient application which provides the user data in reaction to thereceived input data provided by the host computer. In providing the userdata, the executed client application may further consider user inputreceived from the user. Regardless of the specific manner in which theuser data was provided, the UE initiates, in an optional third substep1130, transmission of the user data to the host computer. In a fourthstep 1140 of the method, the host computer receives the user datatransmitted from the UE, in accordance with the teachings of theembodiments described throughout this disclosure.

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 12will be included in this section. In an optional first step 1210 of themethod, in accordance with the teachings of the embodiments describedthroughout this disclosure, the base station receives user data from theUE. In an optional second step 1220, the base station initiatestransmission of the received user data to the host computer. In a thirdstep 1230, the host computer receives the user data carried in thetransmission initiated by the base station.

FIG. 13 is a block diagram illustrating an example network node 30,which may be configured to operate as a base station. The network node30 may be one of multiple network nodes in a cloud-based system thatcarry out the described techniques. The network node 30 may be, forexample, an eNB or a 5G gNB. The network node 30 provides an airinterface to a wireless device, e.g., 5G air interface for downlinktransmission and uplink reception, which is implemented via antennas 34and transceiver circuitry 36. The transceiver circuitry 36 includestransmitter circuits, receiver circuits, and associated control circuitsthat are collectively configured to transmit and receive signalsaccording to a radio access technology, for the purposes of providingcellular communication, or WLAN services if necessary. According tovarious embodiments, cellular communication services may be operatedaccording to any one or more of the 3GPP cellular standards, GSM, GPRS,WCDMA, HSDPA, LTE, LTE-Advanced and 5G. The network node 30 also includecommunication interface circuitry 38 for communicating with nodes in thecore network, other peer radio nodes, and/or other types of nodes in thenetwork.

The network node 30 also includes one or more processing circuits 32that are operatively associated with and configured to control thecommunication interface circuitry 38 and/or the transceiver circuitry36. The processing circuitry 32 comprises one or more digital processors42, e.g., one or more microprocessors, microcontrollers, Digital SignalProcessors (DSPs), Field Programmable Gate Arrays (FPGAs), ComplexProgrammable Logic Devices (CPLDs), Application Specific IntegratedCircuits (ASICs), or any combination thereof. More generally, theprocessing circuitry 32 may comprise fixed circuitry, or programmablecircuitry that is specially configured via the execution of programinstructions implementing the functionality taught herein or maycomprise some combination of fixed and programmable circuitry. Theprocessor(s) 42 may be multi-core.

The processing circuitry 32 also includes a memory 44. The memory 44, insome embodiments, stores one or more computer programs 46 and,optionally, configuration data 48. The memory 44 provides non-transitorystorage for the computer program 46 and it may comprise one or moretypes of computer-readable media, such as disk storage, solid-statememory storage, or any combination thereof. By way of non-limitingexample, the memory 44 may comprise any one or more of SRAM, DRAM,EEPROM, and FLASH memory, which may be in the processing circuitry 32and/or separate from the processing circuitry 32. In general, the memory44 comprises one or more types of computer-readable storage mediaproviding non-transitory storage of the computer program 46 and anyconfiguration data 48 used by the network node 30. Here,“non-transitory” means permanent, semi-permanent, or at leasttemporarily persistent storage and encompasses both long-term storage innon-volatile memory and storage in working memory, e.g., for programexecution.

In some embodiments, the processing circuitry 32 of one or more networknodes 30 connected to a wireless network is configured to performoperations for handling area update reports with respect to the wirelessnetwork in the techniques described herein.

FIG. 14 illustrates an example of the corresponding wireless device 50that is configured to perform the techniques described herein for thewireless device for handling measurement configurations. The wirelessdevice 50 may also be referred to, in various contexts, as a radiocommunication device, a UE, a target device, a device-to-device (D2D)UE, a machine-type UE or UE capable of machine to machine (M2M)communication, a sensor-equipped UE, a PDA (personal digital assistant),a wireless tablet, a mobile terminal, a smart phone, laptop-embeddedequipment (LEE), laptop-mounted equipment (LME), a wireless USB dongle,a Customer Premises Equipment (CPE), etc.

The wireless device 50 communicates with one or more radio nodes or basestations, such as one or more network nodes 30, via antennas 54 and atransceiver circuitry 56. The transceiver circuitry 56 may includetransmitter circuits, receiver circuits, and associated control circuitsthat are collectively configured to transmit and receive signalsaccording to a radio access technology, for the purposes of providingcellular communication services.

The wireless device 50 also includes one or more processing circuits 52that are operatively associated with and control the radio transceivercircuitry 56. The processing circuitry 52 comprises one or more digitalprocessing circuits, e.g., one or more microprocessors,microcontrollers, DSPs, FPGAs, CPLDs, ASICs, or any mix thereof. Moregenerally, the processing circuitry 52 may comprise fixed circuitry, orprogrammable circuitry that is specially adapted via the execution ofprogram instructions implementing the functionality taught herein or maycomprise some mix of fixed and programmed circuitry. The processingcircuitry 52 may be multi-core.

The processing circuitry 52 also includes a memory 64. The memory 64, insome embodiments, stores one or more computer programs 66 and,optionally, configuration data 68. The memory 64 provides non-transitorystorage for the computer program 66 and it may comprise one or moretypes of computer-readable media, such as disk storage, solid-statememory storage, or any mix thereof. By way of non-limiting example, thememory 64 comprises any one or more of SRAM, DRAM, EEPROM, and FLASHmemory, which may be in the processing circuitry 52 and/or separate fromprocessing circuitry 52. In general, the memory 64 comprises one or moretypes of computer-readable storage media providing non-transitorystorage of the computer program 66 and any configuration data 68 used bythe wireless device 50.

Accordingly, in some embodiments, the processing circuitry 52 of thewireless device 50 is configured to operate in a wireless network andhandle area update reports. The processing circuitry 52 is configured toinitiate an RNAU, responsive to detecting that the wireless device hasentered a cell not belonging to an RNA configured for the wirelessdevice. The processing circuitry 52 is also configured to receive, fromthe wireless network, a message indicating that the wireless device'sattempt to perform the RNAU has been rejected. The message includes oris accompanied by an indication that a wait time value is applicable.The processing circuitry 52 is also configured to, responsive to themessage, set a reject wait timer to the wait time value and perform theRNAU upon expiry of the reject wait timer, by entering an RRC inactivestate from an RRC connected state.

FIG. 15 is a process flow diagram illustrating a corresponding method1500 implemented in the wireless device 50 for handling area updatereports. The method 1500 includes initiating an RNAU, responsive todetecting that the wireless device has entered a cell not belonging toan RNA configured for the wireless device (block 1502). The method 500includes receiving, from the wireless network, a message indicating thatthe wireless device's attempt to perform the RNAU has been rejected, themessage comprising or being accompanied by an indication that a waittime value is applicable (block 1504). The method 500 also includes,responsive to the message, setting a reject wait timer to the wait timevalue (block 1506) and performing the RNAU upon expiry of the rejectwait timer (block 1508). In some embodiments, the wireless device alsosets a periodic RNAU timer to the wait time value, responsive to themessage, and performs the RNAU upon expiry of the reject wait timer andthe periodic RNAU timer.

In some embodiments, the wireless device is in a Radio ResourceConnection (RRC) Inactive state and initiating the RNAU includes sendinga request to resume an RRC connection. The message may include an RRCResume Reject message or an RRC Release message.

In some embodiments, the reject wait timer is the T302 timer specifiedby the 3GPP and the periodic RNAU timer is the T380 timer specified bythe 3GPP.

In some embodiments, the method further comprises tracking the RNAU as apending notification while the reject wait timer is running In someembodiments, setting the periodic RNAU timer to the wait time value maybe responsive to an indication in the message that the periodic RNAUtimer is to be set to the wait time value. The wireless device mayrefrain from performing an RNAU update upon cell reselection prior toexpiry of the reject wait timer.

According to some embodiments, the wireless device 50 is configured toperform another method for handling area update reports. In this case,the processing circuitry 52 is configured to initiate a combined RNAUand TAU, responsive to detecting that the wireless device has entered acell not belonging to an RNA configured for the wireless device and notbelonging to a tracking area configured for the wireless device. Theprocessing circuitry 52 is also configured to receive, from the wirelessnetwork, a message indicating that the wireless device's attempt toperform the combined RNAU and TAU has been rejected, the messagecomprising or being accompanied by an indication that a wait time valueis applicable. The processing circuitry 52 is configured to, responsiveto the message, setting a reject wait timer to the wait time value andsubsequently performing a cell reselection, prior to expiry of thereject wait timer. The processing circuitry 52 is configured toimmediately perform a TAU, subsequent to the cell reselection.

The processing circuitry 52 is also configured to perform acorresponding method 1600, according to some embodiments. The method1600 shown in FIG. 16 includes entering initiating a combined RNAU andTAU, responsive to detecting that the wireless device has entered a cellnot belonging to an RNA configured for the wireless device and notbelonging to a tracking area configured for the wireless device (block1602). The method 1600 includes receiving, from the wireless network, amessage indicating that the wireless device's attempt to perform thecombined RNAU and TAU has been rejected, the message comprising or beingaccompanied by an indication that a wait time value is applicable (block1604). The method 1600 also includes, responsive to the message, settinga reject wait timer to the wait time value (block 1606). The method 1600further includes subsequently performing a cell reselection, prior toexpiry of the reject wait timer (block 1608) and immediately performinga TAU, subsequent to the cell reselection (block 1600).

According to some embodiments, the wireless device 50 is configured toperform another method for handling area update reports. In this case,the processing circuitry 52 is configured to initiate an RNAU,responsive to detecting that the wireless device has entered a cell notbelonging to an RNA configured for the wireless device. The processingcircuitry 52 is configured to receive, from the wireless network, amessage indicating that the wireless device's attempt to perform theRNAU has been rejected, the message comprising or being accompanied byan indication that a wait time value is applicable. The processingcircuitry 52 is further configured to, responsive to the message, set areject wait timer to the wait time value, and notifying the wirelessdevice's RRC layer of the rejection. In some embodiments, the processingcircuitry 52 is further configured to, responsive to the message, set aperiodic RNAU timer to a default value.

The processing circuitry 52 is also configured to perform acorresponding method 1700, according to some embodiments. The method1700 shown in FIG. 17 includes initiating an RNAU, responsive todetecting that the wireless device has entered a cell not belonging toan RNA configured for the wireless device (block 1702). The method 1700also includes receiving, from the wireless network, a message indicatingthat the wireless device's attempt to perform the RNAU has beenrejected, the message comprising or being accompanied by an indicationthat a wait time value is applicable (block 1704). The method 1700further includes, responsive to the message, setting a reject wait timerto the wait time value, and notifying the wireless device's RRC layer ofthe rejection (block 1706). In some embodiments, the method furthercomprises, responsive to the message, setting a periodic RNAU timer to adefault value.

According to some embodiments, the wireless device 50 is configured toperform yet another method for handling area update reports. In thiscase, the processing circuitry 52 is configured to initiate an RNAU,responsive to detecting that the wireless device has entered a cell notbelonging to an RNA configured for the wireless device. The processingcircuitry 52 is also configured to receive, from the wireless network, amessage indicating that the wireless device's attempt to perform theRNAU has been rejected, the message comprising or being accompanied byan indication that a wait time value is applicable. The processingcircuitry 52 is configured to, responsive to the message, track therejected RNAU as a pending notification, such that the rejected RNAU isattempted again as soon as allowed and/or as soon as certain conditionsare met.

The processing circuitry 52 is also configured to perform acorresponding method 1800, according to some embodiments. The method1800 shown in FIG. 18 includes initiating an RNAU, responsive todetecting that the wireless device has entered a cell not belonging toan RNA configured for the wireless device (block 1802). The method 1800also includes receiving, from the wireless network, a message indicatingthat the wireless device's attempt to perform the RNAU has beenrejected, the message comprising or being accompanied by an indicationthat a wait time value is applicable (block 1804). The method 1800further includes, responsive to the message, tracking the rejected RNAUas a pending notification, such that the rejected RNAU is attemptedagain as soon as allowed and/or as soon as certain conditions are met(block 1806).

The method 1800 may further include attempting the rejected RNAU againresponsive to a reject waiter timer expiring. Attempting the rejectedRNAU may be further responsive to determining that the wireless deviceis still camping on a cell outside the RNA configured for the wirelessdevice, when the reject wait timer expires. Attempting the rejected RNAUmay also be further responsive to determining that the rejected RNAU isa combined RNAU and TAU.

In some embodiments, the method 1800 may include attempting the rejectedRNAU again responsive to a cell reselection. Attempting the rejectedRNAU may be further responsive to determining that the cell reselectionis to a cell that is not in the RNAU configured for the wireless device.Attempting the rejected RNAU may be further responsive to determiningthat the rejected RNAU is a combined RNAU and TAU.

In some embodiments, attempting the rejected RNAU again includes sendinga request to resume an RRC connection to the wireless network, therequest to resume an RRC connection indicating that the Resume RRCConnection message corresponds to a pending notification.

In other embodiments, the wireless device is in an RRC Inactive state,and initiating the RNAU comprises sending a request to resume an RRCconnection. The message may include an RRC Resume Reject message or anRRC Release message.

The method 1800 may include continuing to monitor radio access network(RAN) paging according to a stored configuration, subsequent toreceiving the message. The method 1800 may also include monitoring onlycore network (CN) paging, subsequent to receiving the message.

As discussed in detail above, the techniques described herein, e.g., asillustrated in the process flow diagrams of FIGS. 15-18, may beimplemented, in whole or in part, using computer program instructionsexecuted by one or more processors. It will be appreciated that afunctional implementation of these techniques may be represented interms of functional modules, where each functional module corresponds toa functional unit of software executing in an appropriate processor orto a functional digital hardware circuit, or some combination of both.

FIG. 19 illustrates an example functional module or circuit architectureas may be implemented in a wireless device 50. The implementationincludes an initiating module 1902 for initiating an RNAU, responsive todetecting that the wireless device has entered a cell not belonging toan RNA configured for the wireless device. The implementation alsoincludes a receiving module 1904 for receiving, from the wirelessnetwork, a message indicating that the wireless device's attempt toperform the RNAU has been rejected, the message comprising or beingaccompanied by an indication that a wait time value is applicable. Theimplementation also includes a setting module 1906 for, responsive tothe message, setting both a reject wait timer and a periodic RNAU timerto the wait time value and a performing module 1908 for performing theRNAU upon expiry of the reject wait timer and the periodic RNAU timer.

In another example implementation, the initiating module 1902 is forinitiating a combined RNAU and TAU, responsive to detecting that thewireless device has entered a cell not belonging to an RNA configuredfor the wireless device and not belonging to a tracking area configuredfor the wireless device. The receiving module 1904 is for receiving,from the wireless network, a message indicating that the wirelessdevice's attempt to perform the combined RNAU and TAU has been rejected,the message comprising or being accompanied by an indication that a waittime value is applicable. The setting module 1906 is for, responsive tothe message, setting a reject wait timer to the wait time value andre-starting a periodic RNAU timer. The performing module 1908 is forsubsequently performing a cell reselection, prior to expiry of theperiodic RNAU timer and immediately performing a TAU, subsequent to thecell reselection.

In another example implementation, the initiating module 1902 is forinitiating an RNAU, responsive to detecting that the wireless device hasentered a cell not belonging to an RNA configured for the wirelessdevice, and the receiving module 1904 is for receiving, from thewireless network, a message indicating that the wireless device'sattempt to perform the RNAU has been rejected, the message comprising orbeing accompanied by an indication that a wait time value is applicable.The setting module 1906 is for, responsive to the message, setting areject wait timer to the wait time value, setting a periodic RNAU timerto a default value, and notifying the wireless device's RRC layer of therejection.

In another example implementation, the initiating module 1902 is forinitiating an RNAU, responsive to detecting that the wireless device hasentered a cell not belonging to an RNA configured for the wirelessdevice. The receiving module 1904 is for receiving, from the wirelessnetwork, a message indicating that the wireless device's attempt toperform the RNAU has been rejected, the message comprising or beingaccompanied by an indication that a wait time value is applicable. Theimplementation may also include a tracking module 1910 for, responsiveto the message, tracking the rejected RNAU as a pending notification,such that the rejected RNAU is attempted again as soon as allowed and/oras soon as certain conditions are met.

Example Embodiments

Example embodiments of the techniques and apparatus described hereininclude, but are not limited to, the following enumerated examples:

(a). A method, in a wireless device operating in a wireless network, forhandling area update reports, the method comprising:

-   -   initiating a radio network area update (RNAU), responsive to        detecting that the wireless device has entered a cell not        belonging to a radio network area (RNA) configured for the        wireless device;    -   receiving, from the wireless network, a message indicating that        the wireless device's attempt to perform the RNAU has been        rejected, the message comprising or being accompanied by an        indication that a wait time value is applicable;    -   responsive to the message, setting both a reject wait timer and        a periodic RNAU timer to the wait time value; and    -   performing the RNAU upon expiry of the reject wait timer and the        periodic RNAU timer.        (b). The method of example embodiment (a), wherein the wireless        device is in a Radio Resource Connection (RRC) Inactive state,        and wherein initiating the RNAU comprises sending a request to        resume an RRC connection.        (c). The method of example embodiment (b), wherein the message        comprises an RRC Resume Reject message or an RRC Release        message.        (d). The method of any of example embodiments (a)-(c), wherein        the reject wait timer is the T302 timer specified by the        3rd-Generation Partnership Project (3GPP) and the periodic RNAU        timer is the T380 timer specified by the 3GPP.        (e). The method of any of example embodiments (a)-(d), wherein        said setting the periodic RNAU timer to the wait time value is        responsive to an indication in the message that the periodic        RNAU timer is to be set to the wait time value.        (f). The method of any of example embodiments (a)-(e), wherein        the wireless device refrains from performing an RNAU update upon        cell reselection prior to expiry of the reject wait timer.        (g). A method, in a wireless device operating in a wireless        network, for handling area update reports, the method        comprising:    -   initiating a combined radio network area update (RNAU) and        tracking area update (TAU), responsive to detecting that the        wireless device has entered a cell not belonging to a radio        network area (RNA) configured for the wireless device and not        belonging to a tracking area configured for the wireless device;    -   receiving, from the wireless network, a message indicating that        the wireless device's attempt to perform the combined RNAU and        TAU has been rejected, the message comprising or being        accompanied by an indication that a wait time value is        applicable;    -   responsive to the message, setting a reject wait timer to the        wait time value and re-starting a periodic RNAU timer;    -   subsequently performing a cell reselection, prior to expiry of        the periodic RNAU timer; and    -   immediately performing a TAU, subsequent to the cell        reselection.        (h). A method, in a wireless device operating in a wireless        network, for handling area update reports, the method        comprising:    -   initiating a radio network area update (RNAU), responsive to        detecting that the wireless device has entered a cell not        belonging to a radio network area (RNA) configured for the        wireless device;    -   receiving, from the wireless network, a message indicating that        the wireless device's attempt to perform the RNAU has been        rejected, the message comprising or being accompanied by an        indication that a wait time value is applicable;    -   responsive to the message, setting a reject wait timer to the        wait time value, setting a periodic RNAU timer to a default        value, and notifying the wireless device's RRC layer of the        rejection.        (i). A method, in a wireless device operating in a wireless        network, for handling area update reports, the method        comprising:    -   initiating a radio network area update (RNAU), responsive to        detecting that the wireless device has entered a cell not        belonging to a radio network area (RNA) configured for the        wireless device;    -   receiving, from the wireless network, a message indicating that        the wireless device's attempt to perform the RNAU has been        rejected, the message comprising or being accompanied by an        indication that a wait time value is applicable;    -   responsive to the message, tracking the rejected RNAU as a        pending notification, such that the rejected RNAU is attempted        again as soon as allowed and/or as soon as certain conditions        are met.        (j). The method of example embodiment (i), further comprising        attempting the rejected RNAU again responsive to a reject waiter        timer expiring.        (k). The method of example embodiment (j), wherein said        attempting the rejected RNAU is further responsive to        determining that the wireless device is still camping on a cell        outside the RNA configured for the wireless device, when the        reject wait timer expires.        (l). The method of example embodiment (j) or (k), wherein said        attempting the rejected RNAU is further responsive to        determining that the rejected RNAU is a combined RNAU and        tracking area update (TAU).        (m). The method of example embodiment (i), further comprising        attempting the rejected RNAU again responsive to a cell        reselection.        (n). The method of example embodiment (m), wherein said        attempting the rejected RNAU is further responsive to        determining that the cell reselection is to a cell that is not        in the RNAU configured for the wireless device.        (o). The method of example embodiment (m) or (n), wherein said        attempting the rejected RNAU is further responsive to        determining that the rejected RNAU is a combined RNAU and        tracking area update (TAU).        (p). The method of any of example embodiments (j)-(o), wherein        said attempting the rejected RNAU again comprises sending a        request to resume an RRC connection to the wireless network, the        request to resume an RRC connection indicating that the Resume        RRC Connection message corresponds to a pending notification.        (q). The method of any of example embodiments (i)-(p), wherein        the wireless device is in a Radio Resource Connection (RRC)        Inactive state, and wherein initiating the RNAU comprises        sending a request to resume an RRC connection.        (r). The method of example embodiment (q), wherein the message        comprises an RRC Resume Reject message or an RRC Release        message.        (s). The method of any of example embodiments (a)-(q), further        comprising continuing to monitor radio access network (RAN)        paging according to a stored configuration, subsequent to        receiving the message.        (t). The method of any of example embodiments (a)-(q), further        comprising monitoring only core network (CN) paging, subsequent        to receiving the message.        (u). A wireless device adapted to perform the methods of any of        example embodiments (a)-(t).        (v). A wireless device comprising transceiver circuitry and        processing circuitry operatively associated with the transceiver        circuitry and configured to perform the methods of any of        example embodiments (a)-(t).        (w). A computer program comprising instructions that, when        executed on at least one processing circuit, cause the at least        one processing circuit to carry out the method according to any        one of example embodiments (a)-(t).        (x). A carrier containing the computer program of example        embodiment (v), wherein the carrier is one of an electronic        signal, optical signal, radio signal, or computer readable        storage medium.        (y). A communication system including a host computer        comprising:    -   processing circuitry configured to provide user data; and    -   a communication interface configured to forward user data to a        cellular network for transmission to a user equipment (UE)        operating in a wireless network, wherein the UE comprises a        radio interface and processing circuitry, the UE's processing        circuitry configured to:        -   initiate a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, set both a reject wait timer and            a periodic RNAU timer to the wait time value; and        -   perform the RNAU upon expiry of the reject wait timer and            the periodic RNAU timer.            (z). A communication system including a host computer            comprising:    -   processing circuitry configured to provide user data; and    -   a communication interface configured to forward user data to a        cellular network for transmission to a user equipment (UE)        operating in a wireless network, wherein the UE comprises a        radio interface and processing circuitry, the UE's processing        circuitry configured to:        -   initiate a combined radio network area update (RNAU) and            tracking area update (TAU), responsive to detecting that the            UE has entered a cell not belonging to a radio network area            (RNA) configured for the UE and not belonging to a tracking            area configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the combined RNAU and TAU            has been rejected, the message comprising or being            accompanied by an indication that a wait time value is            applicable;        -   responsive to the message, set a reject wait timer to the            wait time value and re-starting a periodic RNAU timer;        -   subsequently perform a cell reselection, prior to expiry of            the periodic RNAU timer; and        -   immediately perform a TAU, subsequent to the cell            reselection.            (aa). A communication system including a host computer            comprising:    -   processing circuitry configured to provide user data; and    -   a communication interface configured to forward user data to a        cellular network for transmission to a user equipment (UE)        operating in a wireless network, wherein the UE comprises a        radio interface and processing circuitry, the UE's processing        circuitry configured to:        -   initiate a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, set a reject wait timer to the            wait time value, setting a periodic RNAU timer to a default            value, and notifying the UE's RRC layer of the rejection.            (bb). A communication system including a host computer            comprising:    -   processing circuitry configured to provide user data; and    -   a communication interface configured to forward user data to a        cellular network for transmission to a user equipment (UE)        operating in a wireless network, wherein the UE comprises a        radio interface and processing circuitry, the UE's processing        circuitry configured to:        -   initiate a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, track the rejected RNAU as a            pending notification, such that the rejected RNAU is            attempted again as soon as allowed and/or as soon as certain            conditions are met            (cc). The communication system of any of example embodiments            (y)-(bb), further including the UE.            (dd). The communication system of any of example embodiments            (y)-(cc), wherein the cellular network further includes a            base station configured to communicate with the UE.            (ee). The communication system of any of example embodiments            (y)-(dd), wherein:    -   the processing circuitry of the host computer is configured to        execute a host application, thereby providing the user data; and    -   the UE's processing circuitry is configured to execute a client        application associated with the host application.        (ff). A method implemented in a communication system including a        host computer, a base station and a user equipment (UE), the        method comprising:    -   at the host computer, providing user data; and    -   at the host computer, initiating a transmission carrying the        user data to the UE via a wireless network comprising the base        station, wherein the method at the UE comprises:        -   initiating a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receiving, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, setting both a reject wait timer            and a periodic RNAU timer to the wait time value; and        -   performing the RNAU upon expiry of the reject wait timer and            the periodic RNAU timer.            (gg). A method implemented in a communication system            including a host computer, a base station and a user            equipment (UE), the method comprising:    -   at the host computer, providing user data; and    -   at the host computer, initiating a transmission carrying the        user data to the UE via a wireless network comprising the base        station, wherein the method at the UE comprises:        -   initiating a combined radio network area update (RNAU) and            tracking area update (TAU), responsive to detecting that the            UE has entered a cell not belonging to a radio network area            (RNA) configured for the UE and not belonging to a tracking            area configured for the UE;        -   receiving, from the wireless network, a message indicating            that the UE's attempt to perform the combined RNAU and TAU            has been rejected, the message comprising or being            accompanied by an indication that a wait time value is            applicable;        -   responsive to the message, setting a reject wait timer to            the wait time value and re-starting a periodic RNAU timer;        -   subsequently performing a cell reselection, prior to expiry            of the periodic RNAU timer; and        -   immediately performing a TAU, subsequent to the cell            reselection.            (hh). A method implemented in a communication system            including a host computer, a base station and a user            equipment (UE), the method comprising:    -   at the host computer, providing user data; and    -   at the host computer, initiating a transmission carrying the        user data to the UE via a wireless network comprising the base        station, wherein the method at the UE comprises:        -   initiating a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receiving, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, setting a reject wait timer to            the wait time value, setting a periodic RNAU timer to a            default value, and notifying the UE's RRC layer of the            rejection.            (ii). A method implemented in a communication system            including a host computer, a base station and a user            equipment (UE), the method comprising:    -   at the host computer, providing user data; and    -   at the host computer, initiating a transmission carrying the        user data to the UE via a wireless network comprising the base        station, wherein the method at the UE comprises:        -   initiating a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receiving, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, tracking the rejected RNAU as a            pending notification, such that the rejected RNAU is            attempted again as soon as allowed and/or as soon as certain            conditions are met.            (jj). The method of any of example embodiments (y)-(bb),            further comprising:    -   at the UE, receiving the user data from the base station.        (kk). A communication system including a host computer        comprising:    -   a communication interface configured to receive user data        originating from a transmission from a user equipment (UE)        operating in a wireless network to a base station, the UE's        processing circuitry configured to:        -   initiate a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, set both a reject wait timer and            a periodic RNAU timer to the wait time value; and        -   perform the RNAU upon expiry of the reject wait timer and            the periodic RNAU timer.            (ll). A communication system including a host computer            comprising:    -   a communication interface configured to receive user data        originating from a transmission from a user equipment (UE)        operating in a wireless network to a base station, the UE's        processing circuitry configured to:        -   initiate a combined radio network area update (RNAU) and            tracking area update (TAU), responsive to detecting that the            UE has entered a cell not belonging to a radio network area            (RNA) configured for the UE and not belonging to a tracking            area configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the combined RNAU and TAU            has been rejected, the message comprising or being            accompanied by an indication that a wait time value is            applicable;        -   responsive to the message, set a reject wait timer to the            wait time value and re-starting a periodic RNAU timer;        -   subsequently perform a cell reselection, prior to expiry of            the periodic RNAU timer; and        -   immediately perform a TAU, subsequent to the cell            reselection.            (mm). A communication system including a host computer            comprising:    -   a communication interface configured to receive user data        originating from a transmission from a user equipment (UE)        operating in a wireless network to a base station, the UE's        processing circuitry configured to:        -   initiate a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, set a reject wait timer to the            wait time value, setting a periodic RNAU timer to a default            value, and notifying the UE's RRC layer of the rejection.            (nn). A communication system including a host computer            comprising:    -   a communication interface configured to receive user data        originating from a transmission from a user equipment (UE)        operating in a wireless network to a base station, the UE's        processing circuitry configured to:        -   initiate a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, track the rejected RNAU as a            pending notification, such that the rejected RNAU is            attempted again as soon as allowed and/or as soon as certain            conditions are met.            (oo). The communication system of any of example embodiments            (kk)-(nn), further including the UE.            (pp). The communication system of any of example embodiment            (kk)-(oo), further including the base station, wherein the            base station comprises a radio interface configured to            communicate with the UE and a communication interface            configured to forward to the host computer the user data            carried by a transmission from the UE to the base station.            (qq). The communication system of any of example embodiments            (kk)-(oo), wherein:    -   the processing circuitry of the host computer is configured to        execute a host application; and    -   the UE's processing circuitry is configured to execute a client        application associated with the host application, thereby        providing the user data.        (rr). The communication system of any of example embodiments        (kk)-(oo), wherein:    -   the processing circuitry of the host computer is configured to        execute a host application, thereby providing request data; and    -   the UE's processing circuitry is configured to execute a client        application associated with the host application, thereby        providing the user data in response to the request data.        (ss). A method implemented in a user equipment (UE), comprising:    -   initiating a radio network area update (RNAU), responsive to        detecting that the UE has entered a cell not belonging to a        radio network area (RNA) configured for the UE;    -   receiving, from the wireless network, a message indicating that        the UE's attempt to perform the RNAU has been rejected, the        message comprising or being accompanied by an indication that a        wait time value is applicable;    -   responsive to the message, setting both a reject wait timer and        a periodic RNAU timer to the wait time value; and    -   performing the RNAU upon expiry of the reject wait timer and the        periodic RNAU timer.        (tt). A method implemented in a user equipment (UE) operating in        a wireless network, comprising:    -   initiating a combined radio network area update (RNAU) and        tracking area update (TAU), responsive to detecting that the UE        has entered a cell not belonging to a radio network area (RNA)        configured for the UE and not belonging to a tracking area        configured for the UE;    -   receiving, from the wireless network, a message indicating that        the UE's attempt to perform the combined RNAU and TAU has been        rejected, the message comprising or being accompanied by an        indication that a wait time value is applicable;    -   responsive to the message, setting a reject wait timer to the        wait time value and re-starting a periodic RNAU timer;    -   subsequently performing a cell reselection, prior to expiry of        the periodic RNAU timer; and    -   immediately performing a TAU, subsequent to the cell        reselection.        (uu). A method implemented in a user equipment (UE) operating in        a wireless network, comprising:    -   initiating a radio network area update (RNAU), responsive to        detecting that the UE has entered a cell not belonging to a        radio network area (RNA) configured for the UE;    -   receiving, from the wireless network, a message indicating that        the UE's attempt to perform the RNAU has been rejected, the        message comprising or being accompanied by an indication that a        wait time value is applicable;    -   responsive to the message, setting a reject wait timer to the        wait time value, setting a periodic RNAU timer to a default        value, and notifying the UE's RRC layer of the rejection.        (vv). A method implemented in a user equipment (UE) operating in        a wireless network, comprising:    -   initiating a radio network area update (RNAU), responsive to        detecting that the UE has entered a cell not belonging to a        radio network area (RNA) configured for the UE;    -   receiving, from the wireless network, a message indicating that        the UE's attempt to perform the RNAU has been rejected, the        message comprising or being accompanied by an indication that a        wait time value is applicable;    -   responsive to the message, tracking the rejected RNAU as a        pending notification, such that the rejected RNAU is attempted        again as soon as allowed and/or as soon as certain conditions        are met.        (ww). The method of any of example embodiments (ss)-(vv),        further comprising:    -   providing user data; and    -   forwarding the user data to a host computer via the transmission        to the base station.        (xx). A method implemented in a communication system including a        host computer, a base station and a user equipment (UE)        operating in a wireless network, the method comprising:    -   at the host computer, receiving user data transmitted to the        base station from the UE, wherein the method comprises, at the        UE:        -   initiating a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receiving, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, setting both a reject wait timer            and a periodic RNAU timer to the wait time value; and        -   performing the RNAU upon expiry of the reject wait timer and            the periodic RNAU timer.            (yy). A method implemented in a communication system            including a host computer, a base station and a user            equipment (UE) operating in a wireless network, the method            comprising:    -   at the host computer, receiving user data transmitted to the        base station from the UE, wherein the method comprises, at the        UE:        -   initiating a combined radio network area update (RNAU) and            tracking area update (TAU), responsive to detecting that the            UE has entered a cell not belonging to a radio network area            (RNA) configured for the UE and not belonging to a tracking            area configured for the UE;        -   receiving, from the wireless network, a message indicating            that the UE's attempt to perform the combined RNAU and TAU            has been rejected, the message comprising or being            accompanied by an indication that a wait time value is            applicable;        -   responsive to the message, setting a reject wait timer to            the wait time value and re-starting a periodic RNAU timer;        -   subsequently performing a cell reselection, prior to expiry            of the periodic RNAU timer; and        -   immediately performing a TAU, subsequent to the cell            reselection.            (zz). A method implemented in a communication system            including a host computer, a base station and a user            equipment (UE) operating in a wireless network, the method            comprising:    -   at the host computer, receiving user data transmitted to the        base station from the UE, wherein the method comprises, at the        UE:        -   initiating a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receiving, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, setting a reject wait timer to            the wait time value, setting a periodic RNAU timer to a            default value, and notifying the UE's RRC layer of the            rejection.            (aaa). A method implemented in a communication system            including a host computer, a base station and a user            equipment (UE) operating in a wireless network, the method            comprising:    -   at the host computer, receiving user data transmitted to the        base station from the UE, wherein the method comprises, at the        UE:    -   initiating a radio network area update (RNAU), responsive to        detecting that the UE has entered a cell not belonging to a        radio network area (RNA) configured for the UE;    -   receiving, from the wireless network, a message indicating that        the UE's attempt to perform the RNAU has been rejected, the        message comprising or being accompanied by an indication that a        wait time value is applicable;    -   responsive to the message, tracking the rejected RNAU as a        pending notification, such that the rejected RNAU is attempted        again as soon as allowed and/or as soon as certain conditions        are met.        (bbb). The method of any of example embodiments (xx)-(aaa),        further comprising:    -   at the UE, providing the user data to the base station.        (ccc). The method of any of example embodiments (xx)-(aaa),        further comprising:    -   at the UE, executing a client application, thereby providing the        user data to be transmitted; and    -   at the host computer, executing a host application associated        with the client application.        (ddd). The method of any of example embodiments (xx)-(aaa),        further comprising:    -   at the UE, executing a client application; and    -   at the UE, receiving input data to the client application, the        input data being provided at the host computer by executing a        host application associated with the client application,    -   wherein the user data to be transmitted is provided by the        client application in response to the input data.        (eee). A communication system including a host computer        comprising:    -   a communication interface configured to receive user data        originating from a transmission from a user equipment (UE)        operating in a wireless network to a base station, the UE's        processing circuitry configured to:        -   initiate a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, set both a reject wait timer and            a periodic RNAU timer to the wait time value; and        -   perform the RNAU upon expiry of the reject wait timer and            the periodic RNAU timer.            (fff). A communication system including a host computer            comprising:    -   a communication interface configured to receive user data        originating from a transmission from a user equipment (UE)        operating in a wireless network to a base station, the UE's        processing circuitry configured to:        -   initiate a combined radio network area update (RNAU) and            tracking area update (TAU), responsive to detecting that the            UE has entered a cell not belonging to a radio network area            (RNA) configured for the UE and not belonging to a tracking            area configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the combined RNAU and TAU            has been rejected, the message comprising or being            accompanied by an indication that a wait time value is            applicable;        -   responsive to the message, set a reject wait timer to the            wait time value and re-starting a periodic RNAU timer;        -   subsequently perform a cell reselection, prior to expiry of            the periodic RNAU timer; and        -   immediately perform a TAU, subsequent to the cell            reselection.            (ggg). A communication system including a host computer            comprising:    -   a communication interface configured to receive user data        originating from a transmission from a user equipment (UE)        operating in a wireless network to a base station, the UE's        processing circuitry configured to:        -   initiate a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, set a reject wait timer to the            wait time value, setting a periodic RNAU timer to a default            value, and notifying the UE's RRC layer of the rejection.            (hhh). A communication system including a host computer            comprising:    -   a communication interface configured to receive user data        originating from a transmission from a user equipment (UE)        operating in a wireless network to a base station, the UE's        processing circuitry configured to:        -   initiate a radio network area update (RNAU), responsive to            detecting that the UE has entered a cell not belonging to a            radio network area (RNA) configured for the UE;        -   receive, from the wireless network, a message indicating            that the UE's attempt to perform the RNAU has been rejected,            the message comprising or being accompanied by an indication            that a wait time value is applicable;        -   responsive to the message, track the rejected RNAU as a            pending notification, such that the rejected RNAU is            attempted again as soon as allowed and/or as soon as certain            conditions are met.            (iii). The communication system of any of example            embodiments (eee)-(hhh), further including the UE.            (jjj). The communication system of any of example            embodiments (eee)-(hhh), further including the base station,            wherein the base station comprises a radio interface            configured to communicate with the UE and a communication            interface configured to forward to the host computer the            user data carried by a transmission from the UE to the base            station.            (kkk). The communication system of any of example            embodiments (eee)-(hhh), wherein:    -   the processing circuitry of the host computer is configured to        execute a host application; and    -   the UE's processing circuitry is configured to execute a client        application associated with the host application, thereby        providing the user data.        (lll). The communication system of any of example embodiments        (eee)-(hhh), wherein:    -   the processing circuitry of the host computer is configured to        execute a host application, thereby providing request data; and    -   the UE's processing circuitry is configured to execute a client        application associated with the host application, thereby        providing the user data in response to the request data.

Notably, modifications and other embodiments of the disclosedinvention(s) will come to mind to one skilled in the art having thebenefit of the teachings presented in the foregoing descriptions and theassociated drawings. Therefore, it is to be understood that theinvention(s) is/are not to be limited to the specific embodimentsdisclosed and that modifications and other embodiments are intended tobe included within the scope of this disclosure. Although specific termsmay be employed herein, they are used in a generic and descriptive senseonly and not for purposes of limitation.

1-33. (canceled)
 34. A method, in a wireless device operating in awireless network, for handling area update reports, the methodcomprising: initiating a radio network area update (RNAU) responsive todetecting that the wireless device has entered a cell not belonging to aradio network area (RNA) configured for the wireless device; receiving,from the wireless network, a message indicating that the wirelessdevice's attempt to perform the RNAU has been rejected, the messagecomprising or being accompanied by an indication that a wait time valueis applicable; responsive to the message, setting a reject wait timer tothe wait time value; and performing the RNAU upon expiry of the rejectwait timer.
 35. The method of claim 34, wherein the wireless device isin a Radio Resource Connection (RRC) Inactive state, wherein initiatingthe RNAU comprises sending a request to resume an RRC connection, andwherein the message comprises an RRC Resume Reject message or an RRCRelease message.
 36. The method of claim 34, where the method furthercomprises, responsive to the message, setting a periodic RNAU timer tothe wait time value, and wherein the method comprises performing theRNAU upon expiry of the reject wait timer and the periodic RNAU timer.37. The method of claim 36, wherein said setting the periodic RNAU timerto the wait time value is responsive to an indication in the messagethat the periodic RNAU timer is to be set to the wait time value. 38.The method of claim 34, wherein the method further comprises trackingthe RNAU as a pending notification while the reject wait timer isrunning.
 39. The method of claim 34, the method further comprising:storing information about the message, the stored information comprisingone or more of any of the following: an incremented counter valueindicating a number of received rejection messages; informationindicating a location where the wireless device when receiving themessage.
 40. The method of claim 39, wherein the information indicatingthe location comprises one or more of any of the following: a physicalcell identifier; a cell identifier; a global cell identifier; and apublic mobile land network (PLMN) identifier.
 41. The method of claim39, further comprising subsequently reporting the stored information tothe wireless network upon entering a connected state.
 42. The method ofclaim 34, the method further comprising: determining that apredetermined number of RNAU attempts have been followed by a networkreject; and upon being allowed to access the network again, performing anetwork access stratum (NAS) recovery.
 43. The method of claim 34, themethod further comprising: determining that a predetermined number ofRNAU attempts have been followed by a network reject; and upon beingallowed to access the network again, performing an inter-frequency cellreselection or inter-RAT cell reselection and attempt a periodic RNAU.44. A method, in a wireless device operating in a wireless network, forhandling area update reports, the method comprising: initiating acombined radio network area update (RNAU) and tracking area update (TAU)responsive to detecting that the wireless device has entered a cell notbelonging to a radio network area (RNA) configured for the wirelessdevice and not belonging to a tracking area configured for the wirelessdevice; receiving, from the wireless network, a message indicating thatthe wireless device's attempt to perform the combined RNAU and TAU hasbeen rejected, the message comprising or being accompanied by anindication that a wait time value is applicable; responsive to themessage, setting a reject wait timer to the wait time value;subsequently performing a cell reselection, prior to expiry of thereject wait timer; and immediately performing a TAU, subsequent to thecell reselection.
 45. The method of claim 44, further comprisingrestarting a periodic RNAU timer, responsive to the message, and whereinthe cell reselection is prior to expiry of the periodic RNAU timer. 46.A method, in a wireless device operating in a wireless network, forhandling area update reports, the method comprising: initiating a radionetwork area update (RNAU) responsive to detecting that the wirelessdevice has entered a cell not belonging to a radio network area (RNA)configured for the wireless device; receiving, from the wirelessnetwork, a message indicating that the wireless device's attempt toperform the RNAU has been rejected, the message comprising or beingaccompanied by an indication that a wait time value is applicable;responsive to the message, setting a reject wait timer to the wait timevalue, and notifying the wireless device's RRC layer of the rejection.47. The method of claim 46, wherein the method further comprises,responsive to the message, setting a periodic RNAU timer to a defaultvalue.
 48. A method, in a wireless device operating in a wirelessnetwork, for handling area update reports, the method comprising:initiating a radio network area update (RNAU) responsive to detectingthat the wireless device has entered a cell not belonging to a radionetwork area (RNA) configured for the wireless device; receiving, fromthe wireless network, a message indicating that the wireless device'sattempt to perform the RNAU has been rejected, the message comprising orbeing accompanied by an indication that a wait time value is applicable;responsive to the message, tracking the rejected RNAU as a pendingnotification, such that the rejected RNAU is attempted again as soon asallowed and/or as soon as certain conditions are met.
 49. The method ofclaim 48, further comprising attempting the rejected RNAU againresponsive to a reject waiter timer expiring.
 50. The method of claim49, wherein said attempting the rejected RNAU is further responsive todetermining that the wireless device is still camping on a cell outsidethe RNA configured for the wireless device, when the reject wait timerexpires.
 51. The method of claim 49, wherein said attempting therejected RNAU is further responsive to determining that the rejectedRNAU is a combined RNAU and tracking area update, TAU.
 52. The method ofclaim 48, further comprising attempting the rejected RNAU againresponsive to a cell reselection.
 53. The method of claim 52, whereinsaid attempting the rejected RNAU again is further responsive todetermining that the cell reselection is to a cell that is not in theRNAU configured for the wireless device.
 54. The method of claim 52,wherein said attempting the rejected RNAU is further responsive todetermining that the rejected RNAU is a combined RNAU and tracking areaupdate (TAU).
 55. The method of claim 51, wherein the wireless device isin a Radio Resource Connection (RRC) Inactive state, wherein initiatingthe RNAU comprises sending a request to resume an RRC connection, andwherein the message comprises an RRC Resume Reject message or an RRCRelease message.
 56. A wireless device comprising transceiver circuitryand processing circuitry operatively associated with the transceivercircuitry, the processing circuitry being configured to perform themethod of claim
 34. 57. A wireless device comprising transceivercircuitry and processing circuitry operatively associated with thetransceiver circuitry, the processing circuitry being configured toperform the method of claim
 44. 58. A wireless device comprisingtransceiver circuitry and processing circuitry operatively associatedwith the transceiver circuitry, the processing circuitry beingconfigured to perform the method of claim
 46. 59. A wireless devicecomprising transceiver circuitry and processing circuitry operativelyassociated with the transceiver circuitry, the processing circuitrybeing configured to perform the method of claim 48.